On Nov 23, 2011, at 6:28 PM, Pavel Ivanov wrote: > No, it's not a bug. It's SQL standard that such form of aggregate > query always returns one row. And when there's no rows in the table it > should return NULL (for all aggregate functions except count() which > returns 0). I said it's kind of unexpected because it seems like > max(1) should always return 1 but it turns out it doesn't always do > so.
Right you are. Lets forget about this entire nonsense then :) _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
