Re: [RESEND] Transaction auto-abort causes grief with Spring Framework - Mailing list pgsql-general

From Webb Sprague
Subject Re: [RESEND] Transaction auto-abort causes grief with Spring Framework
Date
Msg-id b11ea23c0708170146t22d8fa45ye9d382d539b615b9@mail.gmail.com
Whole thread Raw
In response to Re: [RESEND] Transaction auto-abort causes grief with Spring Framework  (Tyson Lloyd Thwaites <tyson.lloydthwaites@allianza.com.au>)
Responses Re: [RESEND] Transaction auto-abort causes grief with Spring Framework  (Alban Hertroys <alban@magproductions.nl>)
List pgsql-general
> Pgs... like a warning that you can't do this;
>
> begin
> insert 1 --works
> insert 2 --fails
> commit
>
> row 1 will exist in db (yes, no kidding). This will not work in pg,
> which I now see is obviously correct.

This should either a FAQ for MS-SQL or Spring, but since PG does it
canonically it doesn't actually get asked very frequently ...

Sounds like a nightmare specifically designed for vendor lock-in.  My
condolences.

I am not sure how you can insert into a log even with savepoints,
unless you put the logging statement first and then follow it with the
insert.

pgsql-general by date:

Previous
From: Tyson Lloyd Thwaites
Date:
Subject: Re: [RESEND] Transaction auto-abort causes grief with Spring Framework
Next
From: Hannes Dorbath
Date:
Subject: CREATE RULE.. RETURNING?