Re: [sqlite] Multiple connection to in-memory database

tmpfs looks like the best approach for us since we then can use concurrent transactions using multiple connections from different threads and with good performances. I didn't know /tmp was mounted as a tmpfs. Thanks all for the replies. Vincent Brandon, Nicholas (UK) wrote: >> I would like

Re: [sqlite] Multiple connection to in-memory database

This was the model that I was using. But I found out that I get a table lock for dropping tables for no reason when you do interleave steps for different prepares. Any body needs a proof I can create a test case for you. No I did not forget to do finalize for the prior prepares. The better

Re: [sqlite] Multiple connection to in-memory database

> > I would like to use transactions from separate threads, each > thread having one connection to a single in-memory db. > If your production environment is a modern linux distribution you may find the temporary directory ("/tmp") is already a memory drive using the tmpfs filesystem. If not

Re: [sqlite] Multiple connection to in-memory database

You don't need to open a second connection. The sole connection can be used from any thread. On Tue, Aug 19, 2008 at 6:17 PM, vincent cridlig <[EMAIL PROTECTED]> wrote: > Hi, > > I would like to use transactions from separate threads, each thread having > one connection to a single in-memory

[sqlite] Multiple connection to in-memory database

Hi, I would like to use transactions from separate threads, each thread having one connection to a single in-memory db. I just read in the sqlite doc that in-memory sqlite databases (using sqlite3_open(":memory:", ...)) are private to a single connection. Is there a way to open a second