About orphan

11-20 of 20Refresh
Result
2

ObjectDB version 2.5.7

Version 2.5.7 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
Forum
2

Cascading delete

Is there a configuration parameter to set this? 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 configuration
Forum
2

Foreign key constraint issue

get deleted, whereas I'd want to remove all orphaned child entities (as with a foreign key constraint
Forum
2

Handling deleted references

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

Issue with cascade delete & add/remove

that has been orphaned to another relationship or otherwise attempt to persist it", so in your application you should avoid adding the address again after removal. quasado
Forum
2

Items in list are doubled, when the entity class is not enhanced

order to fix orphan removal). If Customer is not dirty - it doesn't cascade persisting
Forum
2

Optimistic locking: prevent version increment on entity collection attribute

entity removes the Readings from the DB as if I had a cascading remove with orphan remove = true.   I
Forum
2

recovery enabled="false", still creates tablename.odb$ files

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

Unexpected error when loading all entity 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
Issue
2

I can't get cascading delete to work in JDO

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