I'd actually like a compromise. Allow GROUP BY to accept a derived name if no base name exists. I realize that's against spec, but there's no ambiguity (as it otherwise errors out), and does make it much nicer when the derived column is a hairy expression that I end up needing to replicate in the GROUP BY clause.
-----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Richard Hipp Sent: Wednesday, August 14, 2013 3:40 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] name resolutionn in GROUP BY On Wed, Aug 14, 2013 at 3:08 PM, Igor Tandetnik <i...@tandetnik.org> wrote: > > Most DBMS allow sorting (and grouping) by arbitrary expressions, which > means that the standard is not directly applicable. One has to extrapolate. > PostgreSQL, MS-SQL, and SQLite 3.7.15 work one way. Oracle and SQLite 3.7.17 work the other. I think I'm going to revert SQLite to working as does PostgreSQL. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users This email and any attachments are only for use by the intended recipient(s) and may contain legally privileged, confidential, proprietary or otherwise private information. Any unauthorized use, reproduction, dissemination, distribution or other disclosure of the contents of this e-mail or its attachments is strictly prohibited. If you have received this email in error, please notify the sender immediately and delete the original. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
