[
https://issues.apache.org/jira/browse/OPENJPA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133107#comment-18133107
]
ASF subversion and git services commented on OPENJPA-3042:
----------------------------------------------------------
Commit 2d0ec2dd76a2c3e0e908bd2f181f932872ebd3d9 in openjpa's branch
refs/heads/OPENJPA-3042 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=2d0ec2dd7 ]
[OPENJPA-3042] Evaluate EXTRACT in memory with the ISO week and the local date
and time of each temporal type
WEEK was mapped to ALIGNED_DAY_OF_WEEK_IN_YEAR, a day of the week, and is now
the ISO-8601 week of the week based year. A java.sql.Timestamp was read as an
Instant, which has no calendar fields, and java.util.Date, Calendar and
Instant were rejected; they are now read as a local date and time. SECOND
keeps the nanoseconds and EXTRACT of null is null.
> In-memory EXTRACT(WEEK) returns the day of the week
> ---------------------------------------------------
>
> Key: OPENJPA-3042
> URL: https://issues.apache.org/jira/browse/OPENJPA-3042
> Project: OpenJPA
> Issue Type: Sub-task
> Reporter: Richard Zowalla
> Assignee: Richard Zowalla
> Priority: Major
>
> When EXTRACT(WEEK) is evaluated in memory, {{DateTimeExtractField.WEEK}} is
> mapped to {{ChronoField.ALIGNED_DAY_OF_WEEK_IN_YEAR}}, which is a day-of-week
> value (1 to 7), not the ISO week of the year. It should use
> {{IsoFields.WEEK_OF_WEEK_BASED_YEAR}}, matching the SQL side (OPENJPA-3037).
> Found while testing OPENJPA-3029.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
