From: | Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Transaction and SQL errors |
Date: | 2022-04-04 11:33:14 |
Message-ID: | DBAP191MB1289450C733A5A3662C2257EB0E59@DBAP191MB1289.EURP191.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello!
Is there any plan to have an equivalent of psql's
set ON_ERROR_ROLLBACK on
in the DB engine?
Most other DB engines have this behavior built-in, that makes migration to PostgreSQL more difficult when there are complex long transactions in the application code.
I do often suggest programmers to trust the DB engine regarding table constraints, and let the engine check unique / foreign keys, etc. However, these errors cancel the whole transaction and user code can't correct the last SQL statement and try a new execution, without losing everything since TX started...
Any thoughts?
Any arguments I could give to programmers? Maybe:
"You better replay all SQL of the whole transaction... (and make them as short as possible!)"
?
Seb
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2022-04-04 11:37:13 | Re: Transaction and SQL errors |
Previous Message | Arup Nanda | 2022-04-04 08:35:44 | gist segmentation fault |