I need advice about possible issues using DBI/DBD::Oracle (plus DBIx::Class) in a multi-threaded Perl-application on Linux.
Firstly I would like to know whether the whole stack (Oracle client-library, DBD::Oracle ... all the way up to DBIx::Class) is threadsafe at all.
Secondly (assuming it is threadsafe) I wonder if you can establish a database-connection and then start a number of threads (so that each thread then has access to the one connection) or if it would be better not to share the connection between threads but rather have each thread establish it's own connection.
In case DBD::Oracle cannot be used concurrently from several threads would it be possible for just one thread to have a database-connection or do threads and DBD::Oracle just do not mix (I can vaguely remember a warning I once got when DBD::Oracle discovered that my Perl had threading-support compiled in but I may remember wrongly)?
Could you also provide some "gut feeling" on what you think about multi-threaded database-apps - is it something you would consider for a business-critical application?
The reason I ask is that we are currently discussing several options of implementing some project infrastructure and I simply would like to eliminate problematic designs as early as possible.
Many thanks!
In reply to DBD::Oracle and threading by morgon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |