Hibernate reverse engineering procedure generated @Temporal(TemporalType.TIMESTAMP) for DateTime

Question

Fields in a DB were of type DATETIME (mysql).

Why was it generated as a timestamp and will it be regenerated

during object persistence? That is not a desired scenario in my case,

seeing that as not a timestamp field means that it should only be set via setter,

no generation needed, I dont really understand why it did not generate it as Date type!

p.s. The problem as I see in that mysql JDBC driver returns datetime type as TIMESTAMP ! How to resolve all that?

Answer 1

Without knowing the inner workings of hibernate, we have our date fields in the database (mysql) as date. Not DATETIME. Maybe that is why it generated timestamp.

You should consider changing your date tables to date and then you can change your entity beans and remove the @Temporal

In any case, it is probably safe to remove the @Temporal(TemporalType.TIMESTAMP) alltogether from the entity beans if that is not what you want.

Answer 2

The @Temporal annotation denotes, whether annotated property should be mapped to java.sql.Date (holds only date part), java.sql.Time (holds only time part) or to java.sql.Timestamp (holds date and time also with fractions of second). It has nothing to do with generation of property value.

Answer 3

I think of two possibilities: Hibernate does not know about data type "dateTime" for mysql or "dateTime" explicitly mapped to java.sql.Timestamp or java.utils.Date (wich needs TemporalType.Timestamp annotation). And this mapping probably can be changed.