May 28, 2013 at 3:42 am
Easy enough if you know how EXCEPT and related options work.
But don't quite understand the statement "The key to this is of course the use of DISTINCT".
There is no use of DISTINCT, so how can it be the key to anything?
May 28, 2013 at 3:53 am
Toreador (5/28/2013)
But don't quite understand the statement "The key to this is of course the use of DISTINCT".There is no use of DISTINCT, so how can it be the key to anything?
First sentence of the explanation, emphasis mine:
"EXCEPT returns any distinct values from the left query that are not also found on the right query"
May 28, 2013 at 3:55 am
I guess you're right. I'd assumed it meant the keyword DISTINCT, given that it was in uppercase 🙂
June 3, 2013 at 1:01 am
skanker (5/20/2013)
Thanks for the question. It might be easy for others, however I learnt something on this. I did not do my research first and thought it would be three.
Same here.
June 18, 2013 at 7:58 am
Ignored completely the DISTINCT usage
leearned something today
July 5, 2013 at 2:18 am
Easy one. This is according to the SQL standard. Unfortunately, SQL Server does not support except all and intersect all, which both is a part of the SQL Standard. There are times where I really missed them, especially except all.
September 30, 2013 at 3:04 am
Also nice piece of information regarding INTERSECT and EXCEPT: NULL values are regarded as the same. A behaviour as if SET ANSI_NULLS were OFF.
________________________________________________________
If you set out to do something, something else must be done first.
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply