Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider using JodaTime instead of Date/Timestamp #1

Open
nealeu opened this issue Jan 15, 2013 · 0 comments
Open

Consider using JodaTime instead of Date/Timestamp #1

nealeu opened this issue Jan 15, 2013 · 0 comments

Comments

@nealeu
Copy link
Contributor

nealeu commented Jan 15, 2013

Cosmo use of Date is currently flawed when a Timestamp is provided, as Timestamp.after(Timestamp) is not called but instead Date.after(Date) is called on the seconds part of the timestamp object. See http://stackoverflow.com/a/2411168

Additionally, Date has quirky perf characteristics see http://joda-time.sourceforge.net/index.html
nealeu added a commit that referenced this issue Jan 15, 2013
@nealeu
Fix timestamp related test failure
7ff992e 
Due to Timestamp not properly overloading after(Date).

See issue #1 for preferred solution
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nealeu