Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 3 of 3 total |
SQL pdf Manual bug |
Tue, Apr 14 2009 7:57 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | UNION, INTERSECT, and EXCEPT Clauses
By default, non-distinct rows are aggregated into single rows in a UNION, INTERSECT, or EXCEPT operation. Use the ALL clause to retain non-distinct rows. I hope it should read distinct. If not 1) the little test I just tried returns the wrong result and 2) I can't get my head round why Roy Lambert |
Tue, Apr 14 2009 8:10 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< I hope it should read distinct. If not 1) the little test I just tried returns the wrong result and 2) I can't get my head round why >> If you mean the first "non-distinct" reference, then no, it is is correct in the manual. Non-distinct rows are effectively made distinct in a UNION, INTERSECT, or EXCEPT operation. If what you're seeing doesn't jive with that, then send me the test that you're using and I'll take a look. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Apr 14 2009 8:28 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
Its me - typing up a response here did something to my brain and I realised I had distinct and non-distinct reversed - sorry. Roy Lambert |
This web page was last updated on Saturday, May 4, 2024 at 09:18 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |