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-860
Type: Bug Bug
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

Utility method AbstractClassMetaData.pkUsesIdentityStrategy doesn't allow for NATIVE implying use of IDENTITY internally

Created: 22/Jun/12 11:03 AM   Updated: 06/Jul/12 10:00 AM   Resolved: 22/Jun/12 11:04 AM
Component/s: MetaData
Affects Version/s: 3.1.0.m3, 3.1.0.m4
Fix Version/s: 3.1.0.m5

Andy Jefferson added a comment - 22/Jun/12 11:04 AM
SVN trunk fixes this

Andy Jefferson made changes - 22/Jun/12 11:04 AM
Field Original Value New Value
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Chris Colman added a comment - 23/Jun/12 09:10 PM - edited
Would this change have any consequences for apps that don't specify identity strategy and therefore could have defaulted to native?

I'm not sure of the exact details of the issue fixed but is the following scenario possible?

Native was defaulted to but it was identity "implied" because of this issue but now that this issue is fixed native will actually *really* be native.

(We're using MySQL. I'm not sure if DN chooses native or not for that datastore. Is it possible we now might have to explicitly specify 'identity' rather than rely on the default strategy because of this fix?)

Andy Jefferson added a comment - 24/Jun/12 08:43 AM
Youre not using AFAIK MongoDB

Chris Colman added a comment - 26/Jun/12 01:53 PM
Correct, not using MongoDB. We're using MySQL so that means we're unaffected I assume.

Andy Jefferson made changes - 06/Jul/12 10:00 AM
Status Resolved [ 5 ] Closed [ 6 ]