I believe only WAL mode is sticky.
Not using the pragma seems to generate deletions as normal.
The missing data was from after the file was closed. I am still looking into
rollback, but why would journal mode matter?
Marc
On Dec 18, 2012, at 12:02 PM, "Simon Slavin" wrote:
>
> On 18 Dec 2
On 18 Dec 2012, at 3:04pm, Marc L. Allen wrote:
> I also have no additional information as to why having PERSIST mode on
> prevents the database from being updated/correct. I did check the
> sqlite3_close command, and I'm passing it the connection received from
> sqlite3_open. It returns SQ
f SQLite Database
Subject: Re: [sqlite] PERSIST Journal Mode
On 17 Dec 2012, at 8:35pm, "Marc L. Allen" wrote:
> Another item.. when having Journal Mode = PERSIST, DBA (in the example below)
> was not being physically updated. DBB was.
I can think of a reason you might no
On 17 Dec 2012, at 8:35pm, "Marc L. Allen" wrote:
> Another item.. when having Journal Mode = PERSIST, DBA (in the example below)
> was not being physically updated. DBB was.
I can think of a reason you might not be able to see an update until you have
executed _close(). So are you looking
It might be my implementation... it's custom for an embedded OS.
Another item.. when having Journal Mode = PERSIST, DBA (in the example below)
was not being physically updated. DBB was.
Simply taking out the PRAGMA fixed things. Any ideas where I should look?
Marc
-Original Message-
5 matches
Mail list logo