"Adam Megacz" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I have an application that absolutely must not return from a certain > call until the results of an update are safely committed to disk. The > situation above would be considered "not safe". How can I perform an > update and then wait until I am completely certain that the data is on > the disk, regardless of whether or not other selects are still in > progress? Blocking for a long time is okay, returning early is not.
Open a separate connection to the same database, perform the update on this connection. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
