Home/ Questions/Q 6874067
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T04:08:55+00:00

In looking through the Joda-Time Hibernate user guide it appears that there is no

  • 0

In looking through the Joda-Time Hibernate user guide it appears that there is no future support for the SQL DATE type. Since TIMESTAMP is specified to start on Jan 1, 1970 – the only safe transport for dates before 1970 appears to be VARCHAR with PersistentLocalTimeAsString (if one wishes to restrict themselves to the Joda Hibernate library).

As someone who uses DATE (and seeing that Joda Hibernate isn’t) I am wondering if there is some reason I should switch to VARCHAR and PersistentLocalTimeAsString. Ie. what motivated the decision to deprecate PersistentYearMonthDay?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It doesn’t start on 1970, it’s a zero point, but it could be negative. The reason why the PersistentYearMonthDay deprecated is deprecation of YearMonthDay. Motivated as “Use LocalDate which has a much better internal implementation and has been available since 1.3“

    Also, it’s weird, but the source code for the PersistentLocalDate has DATE sql type, while the user guide says TIMESTAMP, try it, maybe just a typo in the user guide.

    • 0