[
https://issues.apache.org/jira/browse/OPENJPA-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121919#comment-13121919
]
Michael Spiro commented on OPENJPA-1979:
----------------------------------------
I opened a duplicate issue OPENJPA-2054.
Pinaki, your patch handles only the case with a string constant but doesn`t
handle numeric constants (beginning with a digit, a dot or a minus sign).
"Null" should also be considered a constant. Shouldn't this be added? I think
the parsing logic should be the same as in MappingInfo.mergeJoinColumn().
> Regression for non-standard joins with constant column values
> --------------------------------------------------------------
>
> Key: OPENJPA-1979
> URL: https://issues.apache.org/jira/browse/OPENJPA-1979
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc, kernel
> Affects Versions: 2.0.0-M1, 2.0.0
> Reporter: Pinaki Poddar
> Attachments: OPENJPA-1979.patch.1.txt, Test-1979.zip
>
>
> The non-standard join can use constant column values by enclosing them in
> single-quote character. This behavior is regressed. The likely cause of this
> regression is new delimiting support for schema elements introduced in JPA
> 2.0. The constant column value used to be detected during schema definition
> based on the assumption of the name being enclosed in single-quote. Due to
> introduction of delimiting capability, the constant value is now enclosed in
> double-quote followed by a single-quote.
> The visible effect is failure to define schema for non-standard join with
> constant values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
