On 11/29/16, Andy Goth <andrew.m.g...@gmail.com> wrote: > > CREATE TABLE x(a); > INSERT INTO x VALUES (1), (2.5), (4), (3), (2); > SELECT min(a)*avg(a), max(a)*avg(a) FROM x; > SELECT a*avg(a) FROM x; > SELECT a*avg(a), min(a)*avg(a), max(a)*avg(a) FROM x; > SELECT a*avg(a), max(a)*avg(a), min(a)*avg(a) FROM x; > > The third and fourth SELECTs hit the once-again-ambiguous case of mixing > max() and min() (there's your tongue-twister for the day). Their > a*avg(a) results are 10.0 and 2.5, respectively, suggesting the > rightmost max() or min() function determines which row is used to > compute bare columns. Do you want to document this behavior, or do you > want to reserve the right to change it later?
That behavior is undefined. We reserve the right to change it. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
