> > > > One of many ways would be to precompute the min/max into a separate > table and then query that table whenever you need the min/max. >
Only if one have full control about how the data changes what with so widespread format as sqlite almost always not the case. I mean without triggers you won't be able to control the moment when someone do mass deletes or inserts with an external admin and these are the points when actual min/max may change. Even the author of the subject can sometimes forget about the fact that his data has such dependency and do something affecting this. I thought at the first moment that Pavel's suggestion on using extra index is very "expensive" in terms of megabytes on the disk, but despite this drawback it's actually more robust. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
