> On 20 Nov 2019, at 20:37, Andy Bennett <andy...@ashurst.eu.org> wrote: > > Hi, > >> Did you try retrieving the data "directly" or do you need the subselect in >> order to maintain compatibility with other SQL dialects that are no longer >> able to retrieve data from the row on which the max was found? > > Thanks Keith! > > I understood that selecting other columns during an aggregate lead to > ill-specific or undefined values in those columns. Does SQLite make more > guarantees than the SQL standard here? Do you have a pointer to the docs as I > tried and failed to find it in there.
There's a small sidenote (that I'm too lazy too find right now) in the select docs that mentions that, in case of using min or max as aggregate, the non-aggregate columns will come from the row that held the min/max value. Kind regards, Merijn
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
