MappedDateTime does not store time portion in Derby 10.4.2.0 #12

Closed
tjweir opened this Issue May 16, 2009 · 6 comments

3 participants

@tjweir
Lift Web Framework member

MappedDateTime does not store time portion in Derby 10.4.2.0

Lighthouse #28: http://liftweb.lighthouseapp.com/projects/26102/tickets/28

@tjweir
Lift Web Framework member

Confirmed that a correctly parsed date with time gets stored with all zeros for the time portion.

@dchenbecker
Lift Web Framework member

MappedDateTime is returning a java.sql.Date instead of a java.sql.Timestamp. This is probably why this is happening, so we'll look at what we can do differently.

@dchenbecker
Lift Web Framework member

I just checked in some code in the wip-dcb-mapper-datetime branch on e9a2f3f85e99e5e4f53611e6892830b9878d4f9a. I've tested with Derby, H2, MySQL and PostgreSQL, so I'm pretty confident that this is working.

@dchenbecker
Lift Web Framework member

Fixes pushed to Master.

@dchenbecker dchenbecker was assigned Mar 1, 2012
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment