[
https://issues.apache.org/jira/browse/OPENJPA-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136683#comment-18136683
]
ASF subversion and git services commented on OPENJPA-3048:
----------------------------------------------------------
Commit ffc2af2addeb047544eef819b7c5873bca240085 in openjpa's branch
refs/heads/OPENJPA-3048 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=ffc2af2ad ]
[OPENJPA-3048] Evaluate JDBC escape date, time and timestamp literals as
temporal values in memory
> JDBC escape date literal is not converted when a query is evaluated in memory
> -----------------------------------------------------------------------------
>
> Key: OPENJPA-3048
> URL: https://issues.apache.org/jira/browse/OPENJPA-3048
> Project: OpenJPA
> Issue Type: Sub-task
> Reporter: Richard Zowalla
> Priority: Major
>
> When a query is evaluated in memory (for example over a candidate
> collection), a JDBC escape literal such as {{\{d '2021-01-03'\}}} reaches the
> expression as the raw string, so {{EXTRACT(YEAR FROM \{d '2021-01-03'\})}}
> fails. The literal class ({{Lit}}) should convert it to a date, time or
> timestamp value as the SQL path does.
> Found while working on OPENJPA-3042.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
