ObjectDB Database Search

, if any). Orphan Removal JPA 2 supports an additional and more aggressive remove cascading mode ... a remove operation. To avoid dangling references as a result of orphan removal this feature should only be enabled for fields that hold private non shared dependent objects. Orphan removal can also be set

.annotations.CascadeType.DELETE_ ORPHAN ) and i applied that as @ManyToMany(fetch = FetchType.EAGER, cascade ... _ ORPHAN ) private List conclusions = new ArrayList (); @ManyToMany( fetch = FetchType.LAZY, cascade = CascadeType.ALL) @Cascade(org.hibernate.annotations.CascadeType.DELETE_ ORPHAN ) private List

the problem. Detecting orphan objects in reflection mode. This is fixed now in build 2.3.7_13. Notice ... of course. But since the 2 modes use separate code in many areas (e.g. detecting orphan entities) bugs

this has no effect... Is there any mistake? Thank you Michael anaq x Orphan removal was not handled ... it. Notice that usually modifications should be done on the owner side, but in the case of orphan removal

file, there are also serious problems in the structure of the database ( orphan pages and pages ... concurrently can cause exactly this issue of structural issues ( orphan pages and page with multiple

(); The volumes of items could be large so I am concerned that I will get a build-up of " orphan " bindings ... . This will also solve the orphan problem.   support Support Yes, I was using Utilities.bind. The reason

between that would remove the orphane references) ?   hgzwicker Hans-Georg Zwicker References ... is there an option to run Doctor without cleaning the orphane objects ? hgzwicker Hans-Georg Zwicker Currently

with orphan remove = true.   I have joined a simple test for you. Thank you for your help and sorry in

. If every Profile instance is owned by exactly one User instance you may consider using orphan

Is there a configuration parameter to set this? dmoshal David Moshal You can set cascade delete using annotations (see also the Orphan Removal section). JDO defines similar annotations, and both JPA and JDO support this setting also in XML files, but no additional parameters exist in ObjectDB

Running in embedded mode, configuration specifies " ".  Still, tablename.odb$ files get created, and if still present after an abrupt stop, the application will not restart properly.   What do we need to do to not utilize recovery files (not have orphan tablename.odb$ files)? CAPdev CAP

_03 and was changed in order to fix orphan removal). If Customer is not dirty - it doesn't cascade

want to remove all orphaned child entities (as with a foreign key constraint). Interestingly

, clearing list fields and keeping orphan objects is the database (if understood correctly) is possible

will be produced. support Support The orphan Position records are there because i deleted some Units with a DELETE ... then tried to delete the orphans . Without success. Try this query: DELETE FROM Position p WHERE p

is that orphan removal does not happen as a result of removing a reference to an object (which becomes an orphan ) using the new methods:  removeIf(predicate) and remove(key, value). support Support

I enclose a Netbeans project which demonstrates the problem.  Cascading persist works, but cascading delete does not, leaving orphan objects. sjzlondon Steve Zara Thank you for this report. Apparently cascading delete has never been implemented in ObjectDB (see also "Deleting Dependent

Added support of report generation using BIRT . Fixed a bug in query optimization of DISTINCT. Fixed a bug in keeping removed entity object in the L2 cache. Fixed orphan removal of owner entity object in bidirectional relationship. Fixed an "Attempt to persist a reference to a non managed instance

Hi, when going through all entity instance to find orphaned entries we get the exception: Exception in thread "main" [ObjectDB 2.6.9_05] Unexpected exception (Error 990)   Generated by Java HotSpot(TM) 64-Bit Server VM 1.8.0_74 (on Windows 10 10.0). Please report this error on http://www

Added Refresh toolbar button and accelerator key in the Explorer. Added support of retrieving database connection details. Fixed unstable activation in Mac OS. Fixed a bug in using FETCH JOIN in criteria queries. Fixed a bug in cascading remove when orphan removal is set. Fixed

upon a specific order of removal, and must not reassign an entity that has been orphaned

. Fixed a bug in detecting orphan entities in reflection mode. Fixed a bug in listing inherited