> This function returns the number of row changes caused by INSERT, UPDATE or >> DELETE statements since the database connection was opened. >> > > Either you're or this sentence on the site should be changed (in the final > part)
Oops, missed the last part. But it seems not very useful for OP because it shows all changes on all trigger levels which can significantly differ from what sqlite3_changes() gives. Pavel On Tue, Mar 2, 2010 at 2:43 PM, Max Vlasov <[email protected]> wrote: > On Tue, Mar 2, 2010 at 6:36 PM, Pavel Ivanov <[email protected]> wrote: > >> OK, now I see the problem, but sqlite3_total_changes() will not help >> here too - it behaves the same way as sqlite3_changes(), it doesn't >> accumulate changes over several statements. >> > > Hmm... are you sure about this? > A quote from the docs: > > This function returns the number of row changes caused by INSERT, UPDATE or >> DELETE statements since the database connection was opened. >> > > Either you're or this sentence on the site should be changed (in the final > part) > > Max > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
