The pool is responsible for maintaining the connections.
An alternative for a connections pool is a process global SQL variable. However for it to work properly all the handlers should be single threaded handlers.
Hi aeric, the single thread is only for the server handler it has nothing to do with the database, the driver and the pooler are in charge of managing that info,
No. Just don't use pooling with SQLite. For SQLite, use the InitializeSQLite method to retrieve your SQL object. Use this single object for all your DB requests. @Erel has provided the code to ensure that only one NonQuery statement will be executed at any given time. This is how I do it in my modified jRDC2 server.
No. Just don't use pooling with SQLite. For SQLite, use the InitializeSQLite method to retrieve your SQL object. Use this single object for all your DB requests. @Erel has provided the code to ensure that only one NonQuery statement will be executed at any given time. This is how I do it in my modified jRDC2 server.
On server apps always set SingleThreaded to false as it refers to the threading method uses on the handler. Setting it to true means that the handler code will run on the main thread. There maybe use cases where it is set to true but I have not encountered this so far.