[
https://issues.apache.org/jira/browse/OPENJPA-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fay Wang updated OPENJPA-793:
-
Attachment: openjpa-793-testcase.patch
> Embeddables does not work properly with duplicate persistent fi
[
https://issues.apache.org/jira/browse/OPENJPA-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fay Wang updated OPENJPA-793:
-
Attachment: openjpa-793-3.patch
The logic to detect duplicate names in the embeddable is moved from
Emb
[
https://issues.apache.org/jira/browse/OPENJPA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fay Wang resolved OPENJPA-742.
--
Resolution: Fixed
Fix Version/s: 2.0.0
> Add line number and column number to QueryMetaData
> -
[
https://issues.apache.org/jira/browse/OPENJPA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651408#action_12651408
]
Fay Wang commented on OPENJPA-742:
--
Patch is committed to openjpa 1.2.x r719275, 1.3.x r7
enhancer throws an exception when parsing column name "first.name" because it
thinks 'first' is a table name
Key: OPENJPA-795
URL: https://issues.apache.o
Jeremy,
Re: incompatible method signatures... I agree. We definitely do need to
address this. Since the spec overrides our implementation, we might just
have a migration issue for our customers. Hopefully, this hasn't been used
extensively. Maybe we should open a sub-task JIRA issue to keep t
