> Any ideas about how to implement a DB in shared memory? It's impossible with current SQLite code base. Even if you try to implement your own database cache and will allocate it in some shared memory it won't work because along with cache pages SQLite also stores some internal information which should be bound to one process.
So your best shot is to re-write SQLite's part related to shared cache and use some inter-process locks there instead of mutexes (they are there used now). Probably this approach will work. But the best solution will be to use standard IPC mechanisms and to not make things over-complicated. Generally databases should be used if you need at least some kind of persistence between process restarts. Pavel On Sun, May 9, 2010 at 8:01 PM, Manuj Bhatia <manujbha...@gmail.com> wrote: > Hi, > > I am trying to implement a shared queue (to asynchronously exchange messages > between processes) using SQLite. > Since I do not need my queues to be persistent (at least for now), I do not > want to use disk based SQLite database (for better performance). > > I see there is an option to create purely in-memory DBs, but I don't see > anything for the shared memory. > Any ideas about how to implement a DB in shared memory? > > Thanks, > Manuj > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
