On Thu, Mar 01, 2001 at 08:03:29PM +, Peter Mount wrote:
> They have to wait as there is only one physical network connection. To get
> round this, you need to use a Connection pool.
After the information I got here, I arrived at that, too. However,
explicitly releasing a resource (as is nec
At 02:20 25/02/01 +0100, Ingo Luetkebohle wrote:
>Hiya,
>
>how good is concurrency supported in the JDBC driver? For example, if
>I have a small process with about 50 threads, some of them requesting
>large objects, will one JDBC connection suffice? If one thread is
>executing a large select which
Ingo Luetkebohle writes:
> how good is concurrency supported in the JDBC driver? For example, if
> I have a small process with about 50 threads, some of them requesting
> large objects, will one JDBC connection suffice? If one thread is
> executing a large select which takes seconds to execute, w
Hiya,
how good is concurrency supported in the JDBC driver? For example, if
I have a small process with about 50 threads, some of them requesting
large objects, will one JDBC connection suffice? If one thread is
executing a large select which takes seconds to execute, will other
threads be able t
