Hi Jason,

> You don't have to start a new connection for each thread. You
> just have to
> make sure that only one thread is working with a connection at a time.

of course you can make sure that only one thread is working with
a connection at a time by adapting your application logic to this
flaw or by using mutexes.

But I don't think this is what multithreading is about, do you agree?
If you use several threads for _database operations_, you have to use
several connections, because otherwise, all of your threads would be
waiting (a long time) for the one accessing the connection object.
So there would be no advantage of using threads in this way.


With regards,
Christian