I understand that 0001 is before 1580 and so weird leap year rules apply. I
need a way to disable this. The problem is that we pull a marker date from
the database (01-01-0001 implies "open-ended-begin-date" while 01-01-9999
implies open ended end date)
When joda loads one of these from the database is decrements the value by
two days. Hibernate then sees that the value has changed and updates the
marker value in the database to a new (and invalid) marker which is screwing
up the database in our project.
I'm using tooling that interfaces all of this with other APIs so it's not
feasible to pass a different Chronology into each constructor. Is there a
way to make the default Chronology something that doesn't display this
behavior? For that matter is there some way to over ride DateTime and
DateMidnight to make it stop changing the dates like this?
Thanks,
Jason Henriksen
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Joda-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/joda-interest
