I'd like to suggest that features such as this be implemented with PRAGMA commands whenever possible, the reason being that the new functionality will then be immediately available to folks using non-C bindings, without waiting for an update to a binding package that may or may not occur.
Jim On 5/23/09, Filip Navara <filip.nav...@gmail.com> wrote: > PRAGMA schema_version ... for the second case. > > F. > > On Sat, May 23, 2009 at 4:20 PM, Simon Slavin > <slav...@hearsay.demon.co.uk> wrote: >> >> On 21 May 2009, at 5:59am, Simon Slavin wrote: >> >>> int sqlite3_change_count(sqlite3*) >>> >>> Returns an integer which is incremented whenn a change is made to any >>> table in the database. May be the value stored in bytes 24..27 of >>> file header or something else if that's not what I really want. >> >> Having thought about it some more, I want two different numbers. One >> of them changes when a field changes: INSERT/DELETE/UPDATE. The other >> changes when the schema changes: ALTER/DROP/CREATE. Rather than crowd >> the function library with multiple functions, it might be possible to >> implement it like so: >> >> int sqlite3_change_count(sqlite3*, int cTypes) >> >> when cTypes = 1, you get the number of changes to the schema >> when cTypes = 2, you get the number of changes to fields >> when cTypes = 3, you get the sum of the above two figures >> >> Or possibly 1 and 2 should be the other way around. >> >> Any ideas, criticism, or reasons it can't be done ? >> >> Simon. >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Software first. Software lasts! _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
