Hi, I would like to implement get_affected_rows for the sqlite3 backend, which currently always returns -1. There's support for this in the SQLite3 API, so it should be relatively easy.
I have however two questions: 1) There's sqlite3_changes and sqlite3_total_changes. The difference is that the former does not include changes caused by triggers and foreign key actions, while the latter does. Which one should be used, so that the behavior is consistent with the other backends? http://www.sqlite.org/c3ref/changes.html http://www.sqlite.org/c3ref/total_changes.html 2) Both functions return the changes for the most recently completed SQL statement for the connection. Since get_affected_rows is a function of soci::statement, should I always call sqlite_(total_)changes and save the value in case the user later calls get_affected_rows, or is it OK if the function gives incorrect values in case another statement was executed in the meantime? Best, Mika ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
