4 Commits

Author	SHA1	Message	Date
drh	41148f83c4	Fix a faulty assert() in the "AS" alias resolution logic of the parser. ... FossilOrigin-Name: b5e43602833249aa4b73337bf85b7f308450dab6	2015-04-23 13:37:05 +00:00
drh	0af16ab2c2	Make sure that GROUP BY terms select input column names in preference to ... output column names, in compliance with the SQL standard. Ticket [1c69be2dafc28]. FossilOrigin-Name: f2d175f975cd0be63425424ec322a98fb650019e	2013-08-15 22:40:21 +00:00
drh	e35463b312	Bare identifiers in ORDER BY clauses bind more tightly to output column name, ... but identifiers in expressions bind more tightly to input column names. This is a compromise between SQL92 and SQL99 behavior and is what PostgreSQL and MS-SQL do. Ticket [f617ea3125e9c]. FossilOrigin-Name: c78b357c00a35ed48ce2ffbc041de8d22570d1e2	2013-08-15 20:24:27 +00:00
drh	a3a5bd9b62	Only consider AS names from the result set as candidates for resolving ... identifiers in the WHERE clause if there are no other matches. In the ORDER BY clause, AS names take priority over any column names. Candidate fix for ticket [2500cdb9be]. FossilOrigin-Name: ad53924dcadffb95c6497c46c228c67e8f5370e4	2013-04-13 19:59:58 +00:00