Re: [sqlite] Not reading data in the -wal file? (Not Reproducible)

Thank you to Igor and Richard. I've studied this issue more, and still don't have an answer, although I've not been able to reproduce it either. I'm not using shared cache, and even if I did leave a database connection open, which seems impossible since sqlite3_open(), sqlite3_finalize() and

Re: [sqlite] Not reading data in the -wal file? (Not Reproducible)

On 6/6/2013 6:04 PM, Jerry Krinock wrote: • Launch Process 2. • Launch Process 1. • Add a record in Process 1. Possibly does not COMMIT. • Launch Process 3. • In Process 3, run the query, then terminate. New record is PRESENT. • In Process 2, open database, run the query, checkpoint, and

Re: [sqlite] Not reading data in the -wal file? (Not Reproducible)

On Thu, Jun 6, 2013 at 6:04 PM, Jerry Krinock wrote: > > On 2013 Jun 06, at 13:28, Richard Hipp wrote: > > > My guess is that App1 never actually committed the transaction. Are you > > sure that you ran COMMIT? And are you sure that the COMMIT was >

Re: [sqlite] Not reading data in the -wal file? (Not Reproducible)

On 2013 Jun 06, at 13:28, Richard Hipp wrote: > My guess is that App1 never actually committed the transaction. Are you > sure that you ran COMMIT? And are you sure that the COMMIT was successful? Thank you, Richard. I didn't have a scope on App 1, and it's much more

Re: [sqlite] Not reading data in the -wal file? (Not Reproducible)

On Thu, Jun 6, 2013 at 4:12 PM, Jerry Krinock wrote: > I just spent a couple hours on a really strange problem that went away. > > • Ann sqlite database had 13 rows in one of its tables. > • In App 1, which uses the "C" interface, add a new row. > • In App 2, which also uses the

[sqlite] Not reading data in the -wal file? (Not Reproducible)

I just spent a couple hours on a really strange problem that went away. • Ann sqlite database had 13 rows in one of its tables. • In App 1, which uses the "C" interface, add a new row. • In App 2, which also uses the "C" interface, open that database with sqlite3_open(), then run query "SELECT *