Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
4.1.M1
-
None
Description
This one is from dev@list.
Data inserted in 4.0 can't be updated in 4.1 if optimistic locking for nullable attribute mapped on java primitive type is used. This is because version 4.1 use field-based data objects that store primitive as primitive, thus there can't be nulls.
Can be solved by modifying cgen templates to use boxed type internally for nullable attributes.
Attachments
Issue Links
- links to
