Re: DBI & threads

2010-04-07 Thread Martin Evans
ion seulement et n'aura pas > n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité pour le contenu fourni. > > > > >> Subject: DBI &

Re: DBI & threads

2010-04-07 Thread John Scoles
n seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Subject: DBI & threads From: j...@roqc.no To: dbi-us

RE: DBI & threads

2010-04-07 Thread Martin Gainty
ement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Subject: DBI & threads > From: j...@roqc.no > To: dbi-users

DBI & threads

2010-04-07 Thread jeff
When building DBI with threads enabled there is a warning against using threads. Is this really true - does anyone have any experience using DBI with threads ?

Re: DBI & threads on Win32

2002-02-01 Thread Not Specified
No, this a hand-rolled server. I found a solution that seems to work. Rather than "use"ing DBI at the top level of the script, I "require" it in the child process, after forking. With limited testing, this appears to allow multiple threads to independently access the database. Unfortunately, th

Re: DBI & threads on Win32

2002-01-31 Thread Simon Oliver
Is your server Net::Daemon or PlRPC based? If so then it is that that is causing the problem, not DBI or the DBD. There are reports that this may be fixed in the latest ActiveState Perl. I have not had chance to check this yet. Not Specified wrote: > > I have written a Perl server that acts a

DBI & threads on Win32

2002-01-30 Thread Not Specified
I have written a Perl server that acts as a gateway to a MySQL database. When clients connect, the server forks a child (which connects to the db, processes the client's request, disconnects from the db and exits). This works great under LINUX with real processes. Moving to Windows (2000), I hav

Re: DBI : Threads + DBD::Informix

2001-09-20 Thread Tim Bunce
On Wed, Sep 19, 2001 at 05:49:26PM -0700, Jonathan Leffler wrote: > On Wed, 19 Sep 2001, Tim Bunce wrote: > >On Wed, Sep 19, 2001 at 11:24:39AM -0500, James Maes wrote: > >> On Wednesday 19 September 2001 11:16 am, James Maes wrote: > >> > On Wednesday 19 September 2001 10:51 am, Tim Bunce wrote:

Re: DBI : Threads + DBD::Informix

2001-09-19 Thread Jonathan Leffler
On Wed, 19 Sep 2001, Tim Bunce wrote: >On Wed, Sep 19, 2001 at 11:24:39AM -0500, James Maes wrote: >> On Wednesday 19 September 2001 11:16 am, James Maes wrote: >> > On Wednesday 19 September 2001 10:51 am, Tim Bunce wrote: >> > > Actually the DBI uses a mutex *per driver* thus ensuring that >> >

Re: DBI : Threads + DBD::Informix

2001-09-19 Thread Tim Bunce
On Wed, Sep 19, 2001 at 11:24:39AM -0500, James Maes wrote: > On Wednesday 19 September 2001 11:16 am, you wrote: > > On Wednesday 19 September 2001 10:51 am, Tim Bunce wrote: > > > > > > > Actually the DBI uses a mutex *per driver* thus ensuring that only a > > > single thread can enter each dri

Re: DBI : Threads + DBD::Informix

2001-09-19 Thread James Maes
On Wednesday 19 September 2001 11:16 am, you wrote: > On Wednesday 19 September 2001 10:51 am, Tim Bunce wrote: > > > > Actually the DBI uses a mutex *per driver* thus ensuring that only a > > single thread can enter each driver. But different threads could go > > through the DBI into different d

Re: DBI : Threads + DBD::Informix

2001-09-19 Thread James Maes
On Wednesday 19 September 2001 10:51 am, Tim Bunce wrote: > > Actually the DBI uses a mutex *per driver* thus ensuring that only a single > thread can enter each driver. But different threads could go through the > DBI into different drivers at the same time. > > One subtle point to note: if m

Re: DBI : Threads + DBD::Informix

2001-09-19 Thread Tim Bunce
On Tue, Sep 18, 2001 at 11:02:04PM -0700, Jonathan Leffler wrote: > James Maes wrote: > > > Are the DBD Modules Thread safe, DBD::Informix in particular. > > Define thread-safe? > > DBI single-threads control. > > DBD::Informix is supposed to compile under a Perl compiled with threads > -- let

Re: DBI : Threads + DBD::Informix

2001-09-18 Thread Jonathan Leffler
James Maes wrote: > Are the DBD Modules Thread safe, DBD::Informix in particular. Define thread-safe? DBI single-threads control. DBD::Informix is supposed to compile under a Perl compiled with threads -- let me know if it doesn't. DBD::Informix makes no attempt to use the threaded ESQL/C lib

DBI : Threads

2001-09-14 Thread James Maes
Are the DBD Modules Thread safe, DBD::Informix in particular. Thanks -- || James Maes || Senior Programmer || [EMAIL PROTECTED] || The Sporting News || www.sportingnews.com || fantasy.sportingnews.com || radio.sportingnews.com ---