2010/11/11 Drake Wilson <dr...@begriffli.ch> > > It looks like you're right, and the resulting row selected is only > arbitrary (though often the one with the largest rowid). This > suggests that unless I'm misunderstanding the comparison, comparing > SQLite's behavior of permitting this type of SELECT with Postgres's > DISTINCT ON (as an earlier post in this thread did) is misleading, > since DISTINCT ON is guaranteed to be semantically after ORDER BY > processing and therefore allows controlling which row from a group is > selected, if one is careful. >
Is needed the sub-query with "order by" for this. -- Best regards, Alexey Pechnikov. http://pechnikov.tel/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
