| From: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
|---|---|
| To: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
| Cc: | "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COMMIT leads to ROLLBACK |
| Date: | 2006-05-21 18:31:01 |
| Message-ID: | c2d9e70e0605211131t2f74cb4ah47d6134768f4e1b5@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/21/06, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> wrote:
> One more question comes to mind. IIRC, Oracle doesn't need you to
> rollback the whole transaction if one statement fails (like constarint
> violation in this case)!!! Does the standard dictate that an error in
> a transaction should force a rollback?
>
> I could be wrong about Oracle; I do not have an Oracle
> installation to check, can somebody verify this?
>
> Regards,
> Gurjeet.
>
that is only possible if you use savepoints and we have them in postgres too.
more than that it's beyond spec i think...
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2006-05-21 20:59:40 | FW: iDefense Q2 2006 Vulnerability Challenge |
| Previous Message | Gurjeet Singh | 2006-05-21 18:05:52 | Re: COMMIT leads to ROLLBACK |