On 05/05/2012 08:25 PM, Roger Binns wrote: > Something else you can consider is changing how your program works so that > the user interface isn't slaved to database operations. You can let the > UI queue up work to be done, and then have a background worker thread > actually do the work in the queue. Save the queue in a separate database > so that work can be resumed even if the application crashes or is > terminated. (BTW this is how many mobile apps operate because db > operations can take quite a while and they also have to be synced to a > server over uncertain network connections.)
I use Sqlite as a document-file. Saving is when user requests to or when program quits. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
