|
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
|
