|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, April 23, 2013 5:32 AM
Points: 138,
Visits: 234
|
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:43 AM
Points: 310,
Visits: 983
|
|
Shouldnt this be
SELECT C.CATID, COUNT(*) FROM #DATA DINNER JOIN #CATEGORY C ON (C.VAL1 = DINNER.VAL1) OR (C.VAL1 IS NULL) GROUP BY C.CATID
(was ON C.VAL1 = D.VAL1)
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Wednesday, September 24, 2008 1:27 PM
Points: 350,
Visits: 229
|
|
ian treasure (8/26/2008) Shouldnt this be
SELECT C.CATID, COUNT(*) FROM #DATA DINNER JOIN #CATEGORY C ON (C.VAL1 = DINNER.VAL1) OR (C.VAL1 IS NULL) GROUP BY C.CATID
(was ON C.VAL1 = D.VAL1)
Nope, its this:
SELECT C.CATID, COUNT(*) FROM #DATA D INNER JOIN #CATEGORY C ON (C.VAL1 = DVAL1) OR (C.VAL1 IS NULL) GROUP BY C.CATID
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:43 AM
Points: 310,
Visits: 983
|
|
| AAAAAA. Knew there was something I'd missed.
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Tuesday, December 04, 2012 11:16 AM
Points: 477,
Visits: 389
|
|
ian treasure (8/26/2008) Shouldnt this be
SELECT C.CATID, COUNT(*) FROM #DATA DINNER JOIN #CATEGORY C ON (C.VAL1 = DINNER.VAL1) OR (C.VAL1 IS NULL) GROUP BY C.CATID
(was ON C.VAL1 = D.VAL1) You must be like me ... always thinking of food
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, April 23, 2013 5:32 AM
Points: 138,
Visits: 234
|
|
hey,
here is the details,
1) inner join or join, its behavior is same, so there will be no effect if you replace inner join with join.
2) parenthesis will not change its behavior, because we have only two conditions in where clause to check, parenthesis will play role when you will have multiple combination of OR and AND operators.
so, i believe code is correct, :)
Tariq master your setup, master yourself. http://mssqlsolutions.blogspot.com
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Yesterday @ 6:41 AM
Points: 2,440,
Visits: 713
|
|
| There was also that new grin nullgroup means no one invited keyword NULLGROUP not far from the DINNER subquery.
Jamie
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Yesterday @ 4:52 PM
Points: 2,548,
Visits: 17,353
|
|
mmmmm.... Dinner Join.... sounds like an invitation to a barbeque.
Reminds me of the QOD from 12/13/07 that used a MIDDLE JOIN. :)
Chad
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Wednesday, September 24, 2008 1:27 PM
Points: 350,
Visits: 229
|
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Thursday, February 07, 2013 12:08 PM
Points: 441,
Visits: 92
|
|
skyline666 (8/26/2008)
ian treasure (8/26/2008) Shouldnt this be
SELECT C.CATID, COUNT(*) FROM #DATA DINNER JOIN #CATEGORY C ON (C.VAL1 = DINNER.VAL1) OR (C.VAL1 IS NULL) GROUP BY C.CATID
(was ON C.VAL1 = D.VAL1)Nope, its this: SELECT C.CATID, COUNT(*) FROM #DATA D INNER JOIN #CATEGORY C ON (C.VAL1 = DVAL1) OR (C.VAL1 IS NULL) GROUP BY C.CATID
When you're copying the code to query window remember to add proper line brakes so you don't end up with "DINER Join" . Must've been hungry? Thanks for the laughs
|
|
|
|