On Thu, 5 Jan 2017 18:56:13 +0100 Simone Mosciatti <sisciamir...@yahoo.com> wrote:
> I could store in some buffer some SQL statement and I could execute > all of them in one single transaction. That's a good idea, all things being equal. But are they equal? Your problem description is entirely technical. It doesn't address how transactions map onto the problem domain. Question you should ask yourself: 1. What is the unit of work? What combinations of operations constitute a logically consistent change to the database? 2. How many units of work are you prepared to lose in the event of system failure? That determines how often you commit. > 2) I need some way to indicate if an error occurs during a write > operation, which is a problem I am not able to solve in a reasonable > bound of complexity. I'm not sure I understand. SQLite will commit the transaction atomically. If the transaction fails for logical or physical reasons, the error is indicated at commit time. How is indicating that error to the user in any way difficult? --jkl _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
