-
Recently Browsing 0 members
- No registered users viewing this page.
-
Similar Content
-
Learn Java with Projects (worth $44.99) but free in exchange for your email
By News Staff,
- packt
- ebook offer
- (and 2 more)
- 0 replies
- 2 views
-
JavaScript from Frontend to Backend ($20.99 Value) FREE for your work email
By News Staff,
- ebook offer
- sponsored
- (and 3 more)
- 0 replies
- 2 views
-
- 0 replies
- 2 views
-
Job Ready Java ($24 value) free download for a Limited Time
By News Staff,
- ebook offer
- java
- (and 1 more)
- 0 replies
- 2 views
-
Transitioning to Java ($35.99 Value) FREE eBook download
By News Staff,
- sponsored
- ebook offer
- (and 1 more)
- 0 replies
- 2 views
-
Question
Lord Method Man
We're working on a web-based application running JSF on a JBoss server. It deals with a lot of dates which are being problematic.
In the Java beans the dates are handled as Date objects and are being stored in a database. Whenever a Date is stored in the database it is changed to -2 days from what it was in Java. (I.E. If the Date object in the bean is May 8, 2012 the Date in the database will be May 6, 2012; if the Java Date is Jan 1, 2010 the database date is Dec 30, 2009).
When the Dates are retrieved from the database they remain off by 2 days. Obviously there is a conflict between how Java and SQL handle date objects and we would like to find a good fix for it.
Here are a couple work-arounds we are considering should a "proper" solution not exist:
- Add 2 days to each Java date before calling the stored procedure
- Convert the Java date to a string before storing it and have SQL convert the string to a date
Has anyone encountered this before or could explain why it is doing this, and if so is there a correct solution for it?
Link to comment
Share on other sites
3 answers to this question
Recommended Posts