Re: [sqlite] PERSIST Journal Mode

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"

Re: [sqlite] PERSIST Journal Mode

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

Re: [sqlite] PERSIST Journal Mode

se Subject: Re: [sqlite] PERSIST Journal Mode On 17 Dec 2012, at 8:35pm, "Marc L. Allen" <mlal...@outsitenetworks.com> 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 rea

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 not be able to see an update until you have executed

[sqlite] PERSIST Journal Mode

I'm having some unexpected results using PRAGMA journal_mode = PERSIST; My general flow runs something like: open(DBA) PRAGMA journal_mode = PERSIST; ATTACH DBB SQL ... close() If the DBA.journal file exists, it's deleted before the attach (though I haven't identified exactly where. I can if