[
https://issues.apache.org/jira/browse/OPENJPA-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136944#comment-18136944
]
ASF subversion and git services commented on OPENJPA-3048:
----------------------------------------------------------
Commit cfed7ea36d8c2e1fe683bf42b1dd8e831267ef17 in openjpa's branch
refs/heads/master from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=cfed7ea36 ]
[OPENJPA-3048] Evaluate JDBC escape date, time and timestamp literals as
temporal values in memory (#255)
* [OPENJPA-3048] Evaluate JDBC escape date, time and timestamp literals as
temporal values in memory
* [OPENJPA-3048] pattern matching
---------
Co-authored-by: Maxim Solodovnik <[email protected]>
> 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)
