Web App you say....
I imagine you are using some wrapper, possibly a JAVA one, PHP or a
PEARL one, I think your web service may have updated so the supported
wrapper updated with possibly a new default setting or such. Those
wrappers usually have a setting/property called "AutoCommit" which
/might/ be the thing that is messing with you. Try searching for it on
the forums for whatever platform you are using, you are bound to find a
lot of mentions and info on it.
If that doesn't solve your problem, could you hook into the SQLite
logging? Or debug the process (I realize this can be difficult via a
wrapper, but the wrapper itself may have some tricks to accommodate it).
Either way, next time you write in, please mention exactly which
platform, which wrapper (if any) and perhaps the extract of the actual
code that does the calling. Even if it is not an SQLite problem
directly, there are likely many people here who use the same
platform/wrapper that you do (perhaps even the wrapper's author).
Cheers,
Ryan
On 2017/09/24 11:58 PM, bensonbear wrote:
I have an sqlite3 database I use for a web app that I am mostly the sole user
of.
It has been working fine for years, but all of a sudden today, I find that
the app cannot insert and delete items from the database when it needs to.
This is an app with a single thread, and for each command the web client
sends to the server written in python, the server opens a new database
connection/cursor (using module sqlite3) does the queries required, commits,
and closes the connection.
That has always worked.
But today, I found that a sequence of actions done in one function with one
database connection/cursor will not work because the later ones do not see
the changes of the earlier ones. Is my understanding correct that as long
as it is the same connection/cursor, these changes should be seen? And, if
not, how is it that it worked in the past? And, in either case, what could
have happened all of a sudden for it to stop working?
For the time being, I am changing now to commit after every query that makes
any change to the database and things work. But I don't want to do that if
it is not necessary.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
