Hi Simon,
A) In that sqlite_sequence table you mentioned, as an additional column. Always up-to-date.
But sqlite_sequence isn't always created. AFAIK it only exists when one or more table exists with an integer primary key autoincrement.
B) In the tables prepared by SQLite ANALYZE. If you want the rowcount updated, do another ANALYZE.
But then the row count isn't always up-to-date and this would be essentially no different from requesting count(*) as per now.
An extra optional sqlite_rowcount table costs so little that I don't see a motivation to put row count data elsewhere. Also keeping it separate doesn't preclude reading the DB with a previous version of SQLite.
It's just a $0.02 idea of course. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
