I am currently looking at building a Perl object to handle data from a
a database.
I'm not really sure if it is best to have one connection to MySQL and
let the object just deal with its own properties.
Or to allow the object to initiate a DBI connection each time an instance
of the object is
On 3/13/03 6:47 AM, Tom Norwood [EMAIL PROTECTED] wrote:
I am currently looking at building a Perl object to handle data from a
a database.
I'm not really sure if it is best to have one connection to MySQL and
let the object just deal with its own properties.
Or to allow the object to
At 14:47 + 3/13/03, Tom Norwood wrote:
I am currently looking at building a Perl object to handle data from a
a database.
I'm not really sure if it is best to have one connection to MySQL and
let the object just deal with its own properties.
Or to allow the object to initiate a DBI connection
.
-Original Message-
From: Paul DuBois [mailto:[EMAIL PROTECTED]
Sent: 13 March 2003 15:14
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: multiple simultaneous DBI connections?
At 14:47 + 3/13/03, Tom Norwood wrote:
I am currently looking at building a Perl object to handle data from
]
Subject: RE: multiple simultaneous DBI connections?
Paul,
I guess I would see the fact that the script would hold the connection
to MySQL for a shorter period of time, as the most obvious advantage.
As far as OO programming goes the integration of DBI into my object
would assure that a connection
, that's not much of a factor in most cases. It has
very efficient connection establishment.
-Original Message-
From: Paul DuBois [mailto:[EMAIL PROTECTED]
Sent: 13 March 2003 15:14
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: multiple simultaneous DBI connections?
At 14:47 + 3/13
