[
https://issues.apache.org/jira/browse/OPENJPA-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915753#action_12915753
]
Howard commented on OPENJPA-1720:
---------------------------------
I will use your suggested workaround (put version field in parent instead
child). However, this doubles the number of UPDATE queries whenever child
field changes are persisted ... one UPDATE on the parent version field + one
UPDATE on the "dirty" child fields. Can this no-version-field-in-child bug be
fixed so I can avoid this extra overhead?
> MappingTool does not add version column for subclass
> ----------------------------------------------------
>
> Key: OPENJPA-1720
> URL: https://issues.apache.org/jira/browse/OPENJPA-1720
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Howard
> Assignee: Fay Wang
> Attachments: jpa_test.zip, OPENJPA-1720.patch
>
>
> MappingTool does not add version column for subclass
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
