Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: 1.2.2.RELEASE
-
Fix Version/s: None
-
Component/s: @ CORE, PERSISTENCE
-
Labels:
-
Environment:Ubuntu 12.04, JDK 1.6.0_33, Maven 3.0.4, Oracle 10
Description
Execute a reverse engineering in a database table with a column named "version".
Generated property is annotated with @Version, when this column there is not a concurrency control column.
Entity update will modify automatically this value when could store important info.
Also application can crash if version column has no numeric type (varchar in example).
Related task ROO-3254 closed before solution patch created.
I attach a diff patch with a solution:
- Create new command option "disableVersionFields"
- By default work as before (false by default)
- If true, don't generate a "@Version" property (in Entity.aj) when "version" column name found
- Generate "version" property as any other field (in DbManaged.aj and entity *.jspx)
Attachments
Issue Links
- duplicates
-
ROO-3283 Reverse engineer disable versions and generated identifiers
-
- Resolved
-