Jonathan Vanasco wrote:
well yeah. its just a really weird situation that is easy to get into
and not really documented. i'm kind of surprised this didn't happen to
anyone else. maybe i'm just doing things REALLY wrong :)
Connecting with AutoCommit on and turning it off when you want to do
Jonathan Vanasco wrote:
Its a really peculiar thing - apache::dbi does the automatic rollback
at the end of scripts which is great for keeping things clean -- but if
you die for another reason and don't do a rollback, you can get that
implicit commit on the next request serviced by the child.
On Jan 13, 2006, at 10:17 PM, Perrin Harkins wrote:
This shouldn't be an issue in an Apache::DBI situation either, if
you didn't start out with AutoCommit = 1. When you have AutoCommit
turned off, it will do a rollback automatically at the end of every
request. You could manually push that
On Jan 13, 2006, at 10:06 PM, Philip M. Gollucci wrote:
I'll add this to my list of Apache-DBI things to look at ... but
that won't be for about 10 days or so
Thanks.
Have you looked at HandleError/RaiseError combo?
Yeah, I came across that after posting. That should do most of what
Jonathan Vanasco wrote:
This shouldn't be an issue in a non-ApacheDBI situation, because you'd
die on the RaiseError and never commit.
This shouldn't be an issue in an Apache::DBI situation either, if you
didn't start out with AutoCommit = 1. When you have AutoCommit turned
off, it will do a
Jonathan Vanasco wrote:
1 - Someone who understands this better than I - note this in the
Apache::DBI documentation. Probably in this paragraph:
I'll add this to my list of Apache-DBI things to look at ... but that
won't be for about 10 days or so
=current_pod
Transactions:
Bear with me, this is confusing to explain.
I noticed something on Apache::DBI (translated, i lost 2days figuring
out what was going on by trailing mysql query logs , and watching DBI
with a tracelevel )
I'm not sure what's causing this: apache:dbi or dbi , or even mysql
being stupid
th
a) perrin, thanks again.
I checked the DBI pod and source, and couldn't elucidate the info
that i needed. some of the source is above my skillset still.
b)
Here is some:
http://modperlbook.org/html/ch01_02.html
saw that in the print version. there's a bit in the devel cookbook
too, but n
On Mon, 2005-10-17 at 10:27 -0400, Jonathan wrote:
> perrin: great - i couldn't find any documentation on this!
The Apache::DBI source is short and simple, so don't be afraid to read
it if you are wondering about how it handles something. (Not that you
shouldn't ask questions, but reading the sou
Jonathan wrote:
perrin: great - i couldn't find any documentation on this! thanks a ton.
all: can i wishlist some more documentation on the forking process
You write it, I'll commit it :)
--
END
What doesn't kill us can only mak
perrin: great - i couldn't find any documentation on this! thanks a ton.
all: can i wishlist some more documentation on the forking process
maybe something like the compression faq, where we go into detail
about exactly when where why you do things before/after the fork,
show some more exam
Jonathan wrote:
on starting up my webapp, i need to pull some data from mysql that is
in the parent process (pre fork)
pre fork connections are bad though, so i'm wondering:
a_ do i have 2 db connect strings:
1. prefork dbh - instantiated prefork , then disconnect
2. postfork
my webapp is using mysql + apache::dbi to store data
on starting up my webapp, i need to pull some data from mysql that is
in the parent process (pre fork)
pre fork connections are bad though, so i'm wondering:
a_ do i have 2 db connect strings:
1. prefork dbh - instantiated prefork
13 matches
Mail list logo
