"Igor Tandetnik" <[EMAIL PROTECTED]> writes: >> I have an application that absolutely must not return from a certain >> call until the results of an update are safely committed to disk.
> Open a separate connection to the same database, perform the update on > this connection. I am in an environment where the underlying operating system does not provide reliable interprocess file locking (in fact, it flat-out lies). Is this still safe? - a _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
