On 31 Oct 2006 at 13:20, Also Sprach Tim Bunce:
> Reread the mysql docs on InnoDB transaction isolation.
> Then you'll see why a commit works. You could also change the default
> isolation level of your session.
Ah, I see. It's the innodb way of working that's thrown me. It's
different to the rd
Reread the mysql docs on InnoDB transaction isolation.
Then you'll see why a commit works. You could also change the default
isolation level of your session.
Tim.
On Mon, Oct 30, 2006 at 09:42:52AM -, [EMAIL PROTECTED] wrote:
> Linux, mysql 4.1.14, DBI 1.38, DBD mysql 2.9002
>
> Lo,
>
> Thi
Linux, mysql 4.1.14, DBI 1.38, DBD mysql 2.9002
Lo,
This isn't so much much a problem as a "what's the best way to do
it".
I have a daemon (perl webserver) that connects to a mysql db when
it receives a request. I thought, to remove the connection overhead,
that I'd use connect_cached (autoco
