Received: from sfinx.lasting.ro (sfinx.lasting.ro [193.230.239.254]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eADKR1s92357 for ; Mon, 13 Nov 2000 15:27:02 -0500 (EST) (envelope-from cristipp@lasting.ro) Received: from cristipp (cristipp.lasting.ro [193.230.239.37]) by sfinx.lasting.ro (8.11.0/bofh+AntiVir) with SMTP id eADKPKP25096; Mon, 13 Nov 2000 22:25:20 +0200 Message-ID: <004d01c04daf$b11a99e0$25efe6c1@lasting.ro> From: "Cristi Petrescu-Prahova" To: "Edmar Wiggers" , References: Subject: Re: how to continue a transaction after an error? Date: Mon, 13 Nov 2000 22:24:15 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Archive-Number: 200011/102 X-Sequence-Number: 133 Multiple transactions carry a price: one cannot isolate the insertions from other sessions. This is not desirable in my case. The second suggestion is valuable. Thanks, Cristi ----- Original Message ----- From: Edmar Wiggers To: Cristi Petrescu-Prahova ; Sent: Monday, November 13, 2000 10:13 PM Subject: RE: [SQL] how to continue a transaction after an error? > > I believe the known mechanism to cope with errors inside transactions are > savepoints. That doesn't seem to be the case, though. > > If you don't care if some inserts fail, then you have multiple transactions > instead of just one (use autocommit). > > If you want a transaction, check existence before each insert. That's the > way to do it. > > > -----Original Message----- > > I would like to insert a bunch of rows in a table in a > > transaction. Some of > > the insertions will fail due to constraints violation. When this happens, > > Postgres automatically ends the transaction and rolls back all > > the previous > > inserts. I would like to continue the transaction and issue the > > commit/rollback command myself.