Issue Details (XML | Word | Printable)

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

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

Use of version metadata is misleading and leading to errors when handling inherited classes with versions

Created: 13/Jul/11 07:46 PM   Updated: 01/Aug/11 10:23 AM   Resolved: 13/Jul/11 08:58 PM
Component/s: MetaData
Affects Version/s: 2.0.5, 2.1.4, 2.2.4, 3.0.0.m6
Fix Version/s: 3.0.0.release


 Description  « Hide
In AbstractClassMetaData we have "hasVersionStrategy" (which checks if this class itself has defined a strategy), and "getVersionMetaData" (which just returns the metadata defined for this class). Obviously if a superclass exists and defines the metadata for versioning then it should be used (since this one will be null). The majority of store plugins get it wrong and just use this class' metadata. We should remove misleading methods and update store plugins to use the correct method(s)

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 13/Jul/11 08:58 PM
SVN trunk fixes this for Mongodb, hbase, odf, excel, neodatis, db4o, xml (and gae/j)