BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px;
}Thanks to all respondents.
A RAM disk is a good idea, but would require me to jump through too
many hoops to get it approved. Corporate environment, you see :(
For now, I've gone with a disk-based database with a larger cache and
page size. Concurrent reads appear to be working, so I guess the
shared cache is disabled by default . . . ?
Best,
Kent
On Wed 07/04/10 6:47 PM , Alexey Pechnikov [email protected]
sent:
Hello!
On Tuesday 06 April 2010 17:43:47 Kent Boogaart wrote:
> What I'm wondering is whether SQLite flat out doesn't support
> concurrent access to an in-memory database, or perhaps whether I'm
> just doing something wrong. Can anyone confirm whether concurrent
> access to an in-memory database is supported?
Use database on tmpfs (ram disk) for this task. It's not needed to
add
this functionality at SQLite internals.
Best regards, Alexey Pechnikov.
http://pechnikov.tel/
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
