[
https://issues.apache.org/jira/browse/OPENJPA-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
brian yoder updated OPENJPA-2503:
---------------------------------
Description:
The non-standard join can use a numeric value, rather than a column or string
constant. 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.
While the string constant (single quote) has been fixed, the numeric constant
(would not have single quote) is still broken.
The visible effect is failure to define schema for non-standard join with
constant NUMERIC values.
was:
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.
Affects Version/s: (was: 2.0.0)
(was: 2.0.0-M1)
2.3.0
Fix Version/s: (was: 2.3.0)
> Numeric non-standard joins with constant column values broken
> -------------------------------------------------------------
>
> Key: OPENJPA-2503
> URL: https://issues.apache.org/jira/browse/OPENJPA-2503
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc, kernel
> Affects Versions: 2.3.0
> Reporter: brian yoder
> Assignee: Pinaki Poddar
>
> The non-standard join can use a numeric value, rather than a column or string
> constant. 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.
> While the string constant (single quote) has been fixed, the numeric constant
> (would not have single quote) is still broken.
> The visible effect is failure to define schema for non-standard join with
> constant NUMERIC values.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
