Hello,
one possible behaviour would be to rollback the transaction to the last
savepoint, which was set before the current statement (not the
transaction!) began. In this case I could commit all changes which have
passed without an error. I think, this is the default case in Oracle -
is this compliant with the SQL-standard?
Regards, Jens
Frank Joerdens schrieb:
>
> Jarmo Paavilainen wrote:
> [ . . . ]
> > "PostgreSQL*" is postgres whith queries inside transactions. But as long as
> > transactions are broken in PostgreSQL you cant use them in real life (if a
> > query fails inside a transactions block, PostgreSQL "RollBack"s the whole
> > transaction block, and thats broken. You can not convince me of anything
> > else).
>
> What do you think _should_ happen when a query fails inside a transaction block? (I am not
> trying to convince you of anything, just being curious.)
>
> Regards,
>
> Frank
=============================================
Jens Hartwig
---------------------------------------------
debis Systemhaus GEI mbH
10875 Berlin
Tel. : +49 (0)30 2554-3282
Fax : +49 (0)30 2554-3187
Mobil : +49 (0)170 167-2648
E-Mail : jhartwig@debis.com
=============================================