X-Original-To: pgsql-interfaces@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 85BFB475F00 for ; Thu, 6 Feb 2003 18:12:32 -0500 (EST) Received: from bachata.cybertec.at (unknown [62.116.21.146]) by postgresql.org (Postfix) with SMTP id EF5FD476011 for ; Thu, 6 Feb 2003 17:58:06 -0500 (EST) Received: (qmail 32612 invoked from network); 6 Feb 2003 22:58:13 -0000 Received: from unknown (HELO cybertec.at) (62.116.21.147) by 62.116.21.146 with SMTP; 6 Feb 2003 22:58:13 -0000 Message-ID: <3E42EA6C.3020107@cybertec.at> Date: Fri, 07 Feb 2003 00:06:20 +0100 From: =?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Nigel J. Andrews" Cc: pgsql-interfaces@postgresql.org, rlippan@remotelinux.com Subject: Re: Problems with DBI transaction handling References: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/19 X-Sequence-Number: 3640 Hi ... I am using: DBI-1.21.tar.gz DBD-Pg-1.01.tar.gz my problem is that Perl complains about connections which are not closed=20 properly and so forth but the main problem is that transactions don't=20 seem to commit although the entire transaction seems to work fine. Maybe=20 this has to do with SERIALIZABLE mode but it is hard to say. The only=20 thing I am doing is a simple loop doing UPDATEs. I have been using DBI=20 for a long time but this is the first time where transactions are used=20 that heavily (normally we use Pg instead). Maybe I should upgrade to a newer version but it seems as if this does=20 not help in my case. I have no idea. What we really need: A Perl module accessing LibEasy providing an=20 interface to persistent database connections. I am using ApacheDBI at=20 the moment (this seems to work well). Hans Nigel J. Andrews wrote: >On Tue, 4 Feb 2003, Hans-J=FCrgen Sch=F6nig wrote: > >=20=20 > >>Does anybody else have problems with DBI transaction handling? Since=20 >>PostgreSQL 7.3 (most likely) the stuff seems to be broken. Errors occur= =20 >>even if autocommit is set properly and rollbacks are not performed the=20 >>way it should be. >> >>Does anybody have similar problems? This is VERY annoying and should not= =20 >>happen. >>The problem is: There is no other interface around providing persistent= =20 >>connections with Perl/Apache. >> >>Maybe it is worth thinking about a Perl implementation of LibEasy with=20 >>Apache persistent connections. >>=20=20=20=20 >> > >Well I have wasted so much time recently, some of it spent trying to work = out >what DBI was doing. However, that was my lack of knowledge, although I'm s= till >not convinced my tests don't now pass by luck. I'm also using a 7.2.3 serv= er >not 7.3 yet and it's not using the mod_perl persistent connection stuff. > >So in short, I'm not surprised you're having problems but unfortunately I = can't >say I experienced the same problem. Perhaps you could give a small test ca= se >that shows the problem as I'm sure DBI must have been tested against 7.3. > > >=20=20 > --=20 *Cybertec Geschwinde u Schoenig* Ludo-Hartmannplatz 1/14, A-1160 Vienna, Austria Tel: +43/1/913 68 09; +43/664/233 90 75 www.postgresql.at , cluster.postgresql.at=20 , www.cybertec.at=20 , kernel.cybertec.at