The following Topic leads to an Error in RemoteDb:
After setting Unique Key to deferrable initially deferred, ManyValuedAssociation to CascadeTypeAllRemoveOrphan I only got the Exception raised by trying to rollback the transaction:
RemoteDB request error: .../rollback 500 Exception Class: Exception Message: Cannot rollback. Database is not in a transaction.
The previous error, that causes the rollback-exception does not appear in my exception-handling:
.../commit 500 Exception Class: EPgNativeException Message: [FireDAC][Phys][PG][libpq] FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »uk_135f17b3_...«. Schlüssel »(x, y)=(4, 2)« existiert bereits.'.
In my opinion only the unique key-violation should raised to our exception-handling.