On Wed, 25 Feb 2004, Tim Bunce wrote: > On Tue, Feb 24, 2004 at 03:25:09PM -0500, Andrew Pimlott wrote: > > I am using DBD::Pg, and I noticed that after a statement causes an > > error, subsequent statements (until rollback) fail with "current > > transaction is aborted, queries ignored until end of transaction". I > > found some postgres documentation[1] suggesting that it is impossible to > > continue after an error. Is this true for other drivers, and is there > > an official DBI position on this? (I couldn't find any mention in the > > DBI documentation.) > > The official DBI position is that the postgres behaviour seems silly.
Agreed! > An error in a *statement* should rollback the effect of *just that > statement* as if it never happened. You should them be able to > continue within the same transaction doing whatever you want as if > you've never even tried executing the statement that failed. Then > finally you can call commit or rollback on the whole lot. > Somewhat old, but: http://archives.postgresql.org/pgsql-general/2000-02/msg00376.php (musing aloud: I wonder if they would accept a patch that made it configurable?) Rudy
