ruby-plsql about ruby-plsql HOT 4 CLOSED

You cannot reuse one plsql connection in many threads - currently there are no thread-safe updates to shared connection data (like cached procedure metadata).

I am not using and testing ruby-plsql in multi-threaded programs and currently do not recommend to do that.

from ruby-plsql.

I use 1 connection per thread,:

thread.times { |i|
threads[i] = Thread.new {
plsql.connection = OCI8.new(user,password,db)

In the given script I try to simulate many user are calling the the same PL/SQL function.
The dbi interface can handle this behavior but I find plsql is nicer to read and write I tried it this way.As well I found nothing regarding thread restrictions in the documentation.

But any way thx for your Info.

from ruby-plsql.

When you use plsql.connection = ... in two different threads then it updates the same connection for default plsql connection. If you want to establish separate connections then you need to do e.g. plsql(:one).connection = ... and plsql(:two).connection = ... and then later as well use them like plsql(:one).some_procedure and plsql(:two).other_procedure. When you use plsql.connection = ... then it is the same as plsql(:default).connection = ...

So maybe you can try something like plsql("thread#{i}") to ensure that each thread will have own connection.

from ruby-plsql.

Manny Thx it works now like expected

from ruby-plsql.