On Wed, Jan 20, 2010 at 8:52 AM, Max Vlasov <max.vla...@gmail.com> wrote: >> 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. > > 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.
Agreed. While storing the min/max in a separate table may be one of the fastest ways, it is unlikely to be the optimal way, as we do not know all the constraints (e.g. robustness, datatype, table size, use cases) Regards, - Robert _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
