Issue Details (XML | Word | Printable)

Key: NUCRDBMS-705
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Niklas Lönn
Votes: 0
Watchers: 0
Operations

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

getString and setString in BigIntRDMSMapper is implemented incorrect.

Created: 13/Nov/13 03:10 PM   Updated: 19/Nov/13 10:28 AM   Resolved: 14/Nov/13 02:47 PM
Component/s: Types
Affects Version/s: None
Fix Version/s: 3.2.8


 Description  « Hide
We bumped DataNucleus to the latest versions in a project and we previously used our own Mapper for converting strings to longs.
Doing so, we noticed that the new DataNucleus default mapper caused an exception. I guess you copied my example, and I had (cant's explain why) used the super statement, and as a result, we are now calling AbstractDatastoreMapping.getLong(...) instead of BigIntRDBMSMapping.getLong(...), causing a fatal NucleusException.

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 14/Nov/13 02:47 PM
SVN trunk likely does what you want, but then you didn't provide a patch/test so its left to the raiser to test it (and I have no need for persisting a String into such a column)