Bruce,
I assume one will be able to ABORT the current transaction without
aborting the higher transaction and ABORT ALL to abort all if needed.
What syntax will be available to the upper transaction to detect a lower
ABORT?
While there be something à la Java ( try catch)?
JLL
Bruce Momjian wrote:
>
> Jon Swinth wrote:
> > The other feature is to allow transactions to continue without being forced to
> > rollback when a SQL exception occurs. In many applications, a SQL exception
> > is handled and an appropriate alternative generated so the transaction goes
> > on. PostgreSQL does not support this and errors on every call made in the
> > same transaction before calling rollback. Some people are willing and able
> > to adjust there application code to handle this. Many people have long
> > running transactions where this is not easily accomplished or are using a
> > pre-existing application that they can't change.
>
> I am going to try to add nested transactions in 7.4. Will that help
> you?
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania 19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
