> > (You must list all the fields that do not contain an aggregate function > in the group by clause) > > > > The way you wrote it only works if your set enginebehavior setting is 70 > > > > The above is so you can make your sql statement compatible with SQL Server >----------------------- > >Amazing that they added the switch to keep it working in a broken >fashion instead of forcing people to do it properly.
Well there's a small subset of situations where the results of a particular query are completely predictable and it's just annoying to have to echo all the fields in the fields clause in the group by clause when it won't actually affect the validity of the result in a particular KNOWN case. SQL is clunky enough without imposing brain-dead 100% enforcement of its clunkier provisions in all cases. It's up to programmers to know when a query expression is reliable and when it isn't based on the data they know they are dealing with. But I'm from the side of the tracks that believes flexibility in programming languages is good... kinda like that guy who had the commercial where the woman who wanted to free people from a gray lock-step mentality threw the hammer at the screen where Big Brother was speaking... .... ... <snicker> Ken Dibble www.stic-cil.org _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
