Thanks Jorge! We just started using JodaTime and it's definitely everything
we wanted from a Time API. Good Find!!!
On Tue, Mar 31, 2009 at 8:31 PM, Kris Nuttycombe
kris.nuttyco...@gmail.comwrote:
I'm also using joda-time, and very pleased with it. In fact, I use it
in my Lift project -
On Tue, Mar 31, 2009 at 11:10 PM, Timothy Perrett
timo...@getintheloop.euwrote:
chronologies (calendar systems). It's also completely immutable (oh, you
didn't know java.util.Calendar isn't thread-safe? you're lucky to have
never
had to track down that bug).
LOL!!! Its not thread
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
I was on IRC trying to help Clemens with this. The name (MappedDateTime),
targetSQLType (java.sql.Types.TIMESTAMP), and type (extends
MappedField[java.util.Date, _]) of this class suggests millisecond precision
(java.sql.Timestamp and java.util.Date have millisecond precision). However,
methods
For an internal project I used JodaTime, twas a dream.
I have switched to using MappedLong along with Unix time for dates
now.
( hooray for ancedotes! )
On Mar 31, 3:21 pm, Jorge Ortiz jorge.or...@gmail.com wrote:
I was on IRC trying to help Clemens with this. The name (MappedDateTime),
chronologies (calendar systems). It's also completely immutable (oh, you
didn't know java.util.Calendar isn't thread-safe? you're lucky to have never
had to track down that bug).
LOL!!! Its not thread safe!? Thats somewhat of an oversight isnt it...
I'm also using joda-time, and very pleased with it. In fact, I use it
in my Lift project - via JPA with the provided Hibernate extensions
for mapping of DateTime, Period, etc.
Kris
On Tue, Mar 31, 2009 at 1:54 PM, TylerWeir tyler.w...@gmail.com wrote:
For an internal project I used JodaTime,
