- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.5K General Database Discussions
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 394 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
How to handle DB exceptions in a master-detail association (NOT COMPOSITE)
we have a use case with master detail association between entities. We didn't set the association as composite, because of validation reasons.
We have copied the code for master detail posting which is suggested in 220.127.116.11.0. (Chapter: 4.14.7 How to Control Entity Posting Order to Prevent Constraint Violations)
This all works as it should, but the problem occurs if we get an error from the database trigger when posting the data.
In the documentation, there is no sample or code suggested for handling DB application errors.
When the error occurs master losses its children, but after executing query on master iterator the row appears again, but with some mixed values.
This problem only occurs after the master entity is new, after first commit attempt the master entity is somehow not new any more.
Also there is no problem with commited entities (retrieved from DB).
We tried to solve this problem by overriding the handlePostChangesError() on MasterEntityImpl and calling handlePostChangesError on
super and all children, but with no success.
Is there a way to solve this issue? Is there any example on how to handle this kind of errors?
With composite association, on this master-detail association everything works fine.
When posting the records adf creates new records and new RowIterators for children. Does calling hanldePostChangesError even matter?