On 7 Oct 2011, at 5:31pm, Puneet Kishor wrote: > assuming you have some other application level language you are using to get > the data, you could stuff the result set into an array and then report the > highest index of the array which might be faster than doing a second query > for just the count.
I'm trying to save the resources necessary for having SQLite fetch the values which the SELECT would return. Any solution mentioned so far has not done that. To see what I'm after, imagine a use interface which asked the user "Do you really want to see all 50,000 entries that that search would return ?". If this kind of search returns more than 100 records, there's no point in doing it at all. I want to know the "50,000" number while placing the minimum load on the system. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
