On 29 Sep 2016, at 8:59am, Jim Borden <jim.bor...@couchbase.com> wrote:
> There is a web API If you're using a conventional server as the front end to your web service (e.g. Apache, with your code written in PHP/Python/C/whatever) then the server spawns a new process to handle each incoming request. So it's possible for two calls to execute at the same time and you do have to worry about multiprocessing. However, there is a question of how SQLite connections are maintained. Does the web service open some connections when it is started and maintain them throughout its life, or does it create a new connection to answer each PUT or GET ? The answer is important because a savepoint is handled by a specific connection. Close the connection and your savepoint vanishes. Also, depending on how your code is written the server may be sending back the acknowledgement for the PUT first, and then doing the database operations while your program is already moving on to do something else. But that would make it impossible to return a different HTTP response code if the PUT fails. It's more likely that the PUT operation waits until the database connection is finished before returning its HTTP response code, to allow it to report errors. In which case I don't see how your problem could occur. But someone else might. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
