From: | Hannu Krosing <hannu(at)skype(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Commit turns into rollback? |
Date: | 2006-03-17 12:03:02 |
Message-ID: | 1142596983.3819.5.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Ühel kenal päeval, R, 2006-03-17 kell 11:27, kirjutas Peter Eisentraut:
> Am Freitag, 17. März 2006 11:25 schrieb Hannu Krosing:
> > > => commit;
> > > ROLLBACK
> > > ^^^^^^^^
> >
> > Return status tells you what actually happened.
>
> If I send a COMMIT, I want a commit to happen or an error.
You already got several errors.
Any suggestion how to get out of the ERROR state ?
=> begin;
BEGIN
=> blah;
ERROR: ...
=> commit;
ERROR: ...
=> select 1;
ERROR: current transaction is aborted, commands ignored until end of
transaction block
Or would you like a mode where you need explicitly send a ROLLBACK to
get out ?
> > > Even if this is justifiable, this behavior is not documented (in any
> > > obvious place).
> >
> > What would you suggest as an obvious place ?
>
> The COMMIT reference page would be a start.
Good point :)
------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2006-03-17 13:10:40 | Re: Commit turns into rollback? |
Previous Message | Peter Eisentraut | 2006-03-17 10:27:45 | Re: Commit turns into rollback? |