Persisting Joda DateTime instead of Java Date in Hibernate -
There are currently Java date properties in my organizations. I'm starting often using date time for timekeeping and calculation. This means that I have to add my dates to the datetime objects and come back again.
So I was wondering if there is no reason why I have java date objects instead of just storing my Jada DataTime objects?
Please note that these institutions continue through Hibernate, I got the project, but I was also reading on the mailing list that it was not compatible with new versions of hibernation. And it seems that it is not maintained very well.
So I'm thinking that it would be best to just change between date and date time, or if the datetime objects will be wise to continue. My worry is dependent on the poor maintenance library.
EDIT: Note that one of my goals will be better in storing timezone information. To save only one date to save the date in the local timezone as my application can be used globally, I also need to know the time zone. The add-on time hibernate has to be detected in such a way.
I think the use of add datetime is probably a good idea for your Bean property type, Can convert and save the property as the original database date format.
I have personally used the time-hibernate and have no problem with it (we are using Hibernate 3.2.5GA).
If you are worried about the timeout-hibernate, then you can always use it (which I'm sure all addim-hibernate does).
Comments
Post a Comment