On Thu, 6 Mar 2003, Stas Bekman wrote:
re: rollback, the DBD drivers will perform the normal disconnect(), but
without doing the physical disconnect, and normal DESTROY, without destroying
the datastructures which maintain the physical connection, so there shouldn't
be much to change for this
Ask Bjoern Hansen wrote:
On Thu, 6 Mar 2003, Stas Bekman wrote:
re: rollback, the DBD drivers will perform the normal disconnect(), but
without doing the physical disconnect, and normal DESTROY, without destroying
the datastructures which maintain the physical connection, so there shouldn't
be
On Fri, 7 Mar 2003, Stas Bekman wrote:
If the physical connection is still there, would the database server
do a rollback?
If earlier the rollback worked correctly with
$dbh ||= connect();, this will work the same, since it performs the same
operation, but rips off only parts of $dbh,
Ask Bjoern Hansen wrote:
On Fri, 7 Mar 2003, Stas Bekman wrote:
If the physical connection is still there, would the database server
do a rollback?
If earlier the rollback worked correctly with
$dbh ||= connect();, this will work the same, since it performs the same
operation, but rips off only
On Wed, 5 Mar 2003, Stas Bekman wrote:
Great. I've already committed that patch.
Perhaps Ask could load 'Apache::compat' inside Apache::DBI if mp2 is used. Or
to use the mp2 API if mp2 is used.
That seems like it'll be an easy solution. I thought loading
Apache::compat would have global
Ask Bjoern Hansen wrote:
On Wed, 5 Mar 2003, Stas Bekman wrote:
Great. I've already committed that patch.
Perhaps Ask could load 'Apache::compat' inside Apache::DBI if mp2 is used. Or
to use the mp2 API if mp2 is used.
That seems like it'll be an easy solution. I thought loading
Apache
Stas Bekman wrote:
FWIW, we are discussing the internal DBI pooling mechanism at the
dbi-dev list and having already a sort-of-working prototype. So
hopefully there will be no need for Apache::DBI in the near future, as
DBI will be able to handle pooling internally. However it may take some
Perrin Harkins wrote:
Stas Bekman wrote:
FWIW, we are discussing the internal DBI pooling mechanism at the
dbi-dev list and having already a sort-of-working prototype. So
hopefully there will be no need for Apache::DBI in the near future, as
DBI will be able to handle pooling internally.
On Today at 11:16am, SB=Stas Bekman [EMAIL PROTECTED] wrote:
SB FWIW, we are discussing the internal DBI pooling mechanism at the
SB dbi-dev list and having already a sort-of-working prototype. So
SB hopefully there will be no need for Apache::DBI in the near future, as
SB DBI will be able to
.
Great. I've already committed that patch.
Perhaps Ask could load 'Apache::compat' inside Apache::DBI if mp2 is used. Or
to use the mp2 API if mp2 is used.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http
My setup is as follows:
Apache/2.0.44 (Gentoo/Linux) mod_perl/1.99_08 Perl/v5.8.0
mod_perl was built from CVS.
I was interested in getting Apache::DBI to run under mp2. I did read
Ask's message at
http://marc.theaimsgroup.com/?l=apache-modperlm=104225578207460w=2
which leads me to my
FWIW, we are discussing the internal DBI pooling mechanism at the dbi-dev list
and having already a sort-of-working prototype. So hopefully there will be no
need for Apache::DBI in the near future, as DBI will be able to handle pooling
internally. However it may take some time, as the drivers
12 matches
Mail list logo
