[
https://issues.apache.org/jira/browse/LANG-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated LANG-400:
-------------------------------
Description:
The JDK contains Date.before() and Date.after() but no time-insensitive
versions exist. I am typically in the situation where TIMESTAMP columns are
converted into Date instances and I need to compare dates only for business
rules.
I propose to complement DateUtils.isSameDay:
DateUtils.isBeforeDay
DateUtils.isAfterDay
My private implementations convert Date to Calendar, zero-out the time
elements, and then compare.
PS: I would also deprecate isSameXXX methods in 2.4 and rename it to isEqualXXX
since sameness usually implies instance equality, rather than object equality.
was:
The JDK contains Date.before() and Date.after() but no time-insensitive
versions exist. I am typically in the situation where TIMESTAMP columns are
converted into Date instances and I need to compare dates only for business
rules.
I propose to complete DateUtils.isSameDay:
DateUtils.isBeforeDay
DateUtils.isAfterDay
My private implementations convert Date to Calendar, zero-out the time
elements, and then compare.
PS: I would also deprecate isSameXXX methods in 2.4 and rename it to isEqualXXX
since sameness usually implies instance equality, rather than object equality.
> Add DateUtils methods to implement before and after time-insensitive
> --------------------------------------------------------------------
>
> Key: LANG-400
> URL: https://issues.apache.org/jira/browse/LANG-400
> Project: Commons Lang
> Issue Type: New Feature
> Affects Versions: 2.3
> Reporter: Paul Benedict
> Fix For: 2.4
>
>
> The JDK contains Date.before() and Date.after() but no time-insensitive
> versions exist. I am typically in the situation where TIMESTAMP columns are
> converted into Date instances and I need to compare dates only for business
> rules.
> I propose to complement DateUtils.isSameDay:
> DateUtils.isBeforeDay
> DateUtils.isAfterDay
> My private implementations convert Date to Calendar, zero-out the time
> elements, and then compare.
> PS: I would also deprecate isSameXXX methods in 2.4 and rename it to
> isEqualXXX since sameness usually implies instance equality, rather than
> object equality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
