From: | "Cristi Petrescu-Prahova" <cristipp(at)lasting(dot)ro> |
---|---|
To: | "Edmar Wiggers" <edmar(at)brasmap(dot)com>, <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: how to continue a transaction after an error? |
Date: | 2000-11-13 20:24:15 |
Message-ID: | 004d01c04daf$b11a99e0$25efe6c1@lasting.ro |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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 <edmar(at)brasmap(dot)com>
To: Cristi Petrescu-Prahova <cristipp(at)lasting(dot)ro>;
<pgsql-sql(at)postgresql(dot)org>
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Teter | 2000-11-14 02:22:41 | Re: Using a postgres table to maintain unique id? |
Previous Message | Marten Feldtmann | 2000-11-13 20:18:49 | Re: Using a postgres table to maintain unique id? |