Hi David,

> Start a "savepoint" before each sub-update and rollback to the savepoint if 
> the update fails, and then try again with different data.  If it succeeds you 
> then release the savepoint anad move on.

Yeah... not ideal in my case & will result in "messy" code...

Would be nice to have an option in PostgreSQL something along the lines
of:  'abort-transaction-on-constraint-violation = false'....

Jan


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to