(Apologies if this doesn't end up in the correct message thread.) > In CONFIG_MULTITHREAD mode, you are responsible for serializing calls > on a single database handle and its statement handles yourself. If you > make calls on a single database handle from two or more threads > simultaneously > the application will likely crash or malfunction. > > The degree of concurrency provided is the same in either case, just > that > in CONFIG_MULTITHREAD mode you are responsible for enforcing it > yourself.
The two scenarios I'm trying to compare are: 1) CONFIG_SERIALIZED with a single, shared database handle. 2) CONFIG_MULTITHREAD with each thread opening its own unshared database handle. Will option 2, at least in theory, allow more concurrency for multiple reader threads? Thanks for your help. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
