Well, I guess this bug needs updated:
http://liftweb.lighthouseapp.com/projects/26102-lift/tickets/28-mappeddatetime-does-not-store-time-portion-in-derby-10420
I would vote for JodaTime. Having written some scheduling apps in Java all I
can say about java.util.{Date,Calender} is WTF?
Derek
On Tue, Mar 31, 2009 at 12:58 PM, Clemens Oertel
<clemens.oer...@gmail.com>wrote:
>
> While trying to figure out why my MappedDateTime fields get stored in
> the DB with all the time info set to 0, I noticed the following:
>
> MappedDateTime (v. 1.0) "claims" to be a TimeStamp: def targetSQLType
> = Types.TIMESTAMP. However, it uses java.sql.Date for its JDBC-
> friendly converted version, not java.sql.TimeStamp. If I read the
> java.sql.Date documentation correctly, java.sql.Date does set all time
> information to 0, since the SQL DATE type only stores dates, by no
> times.
>
> Any comment whether this might have something to do with me losing my
> time would be appreciated.
>
> Best,
> Clemens
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---
