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-1092
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 0

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

Add metadata check for the situation where the user has primary-key fields in superclass and defines another in a subclass

Created: 16/Dec/13 02:29 PM   Updated: 17/Dec/13 08:19 AM   Resolved: 16/Dec/13 02:49 PM
Component/s: MetaData
Affects Version/s: None
Fix Version/s: 3.2.11

 Description  « Hide
When the user defines
public class RootClass
    long id;
public class SubClass extends RootClass
    long id;
it results in an error but in some obscure place down in schema mapping; we should detect this when loading the metadata

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 16/Dec/13 02:49 PM
GitHub master has a check for this situation during metadata loading