DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Key: NUCCORE-1013
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
DataNucleus Core

Delete of object with embedded which has related (non-embedded) object and using cascade delete causes NoTableManagedException

Created: 15/Mar/13 09:45 AM   Updated: 06/Apr/13 09:59 AM   Resolved: 15/Mar/13 09:54 AM
Component/s: Persistence
Affects Version/s: 1.1.6, 2.0.5, 2.1.4, 2.2.4, 3.0.11, 3.1.4, 3.2.0.release
Fix Version/s: 3.2.2


 Description  « Hide
If we have
class A
{
    B b; // embedded
}
class B
{
    C c; // not embedded
}
class C
{
...
}

and we have cascade delete on all relations, then a delete of an A will try to delete the B, which will go through to (org.datanucleus.store.rdbms.request.)DeleteRequest and look for the Table (which doesn't exist). Should just skip that step

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 15/Mar/13 09:54 AM
SVN trunk now handles this case