Ryan writes:
| just to be clear: It's not that SQLite commits after every
| statement - In SQLite, unless you have explicitly opened a
| transaction (using BEGIN), every statement is (and must be)
| in and of itself a transaction.
Right, I didn't say it committed after every statement, just
On Wednesday, 27 September, 2017 00:35, bensonbear
wrote:
>I mentioned I was using python and its sqlite3 module, but did
>not specify I was using it in simplest possible default mode, just
>opening the connection with no arguments.
>I didn't need to know more before --
On 27 Sep 2017, at 7:35am, bensonbear wrote:
> I could not think of anything very useful to try, but in any case I
> found pretty quickly that the problem was the fact that activity
> elsewhere had nearly filled up my root partition. I don't know
> exactly how this
On 2017/09/27 8:35 AM, bensonbear wrote:
I didn't even know that outside transactions, SQLite by
default itself commits automatically after each statement,
which I would not have wanted. However, the python
module by default implicitly inserts "begin"s so that
statements are grouped into a
D.Richard Hipp writes:
| Good question. I suspect that whatever is going wrong has little or
| nothing to do with SQLite, though. What other debugging steps have
| you taken?
I could not think of anything very useful to try, but in any case I
found pretty quickly that the problem was the
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
Are the changes actually making it to the file on disk ? In other words, if
you do _open(), INSERT, _close(), does the disk file get updated ?
What PRAGMAs are you using ?
Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
On 9/24/17, bensonbear wrote:
>
> 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
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
9 matches
Mail list logo