SchemaExport of calendar types - overriding the types

jabley · **Joined:** Wed Jan 23, 2008 8:07 am **Posts:** 6

I'm using the SchemaExportTask ANT task in Hibernate 3.1.3 to export a schema for MySQL and Oracle.

The MySQL create DDL generated maps hibernate calendar types (or java.util.Calendar) to DATETIME SQL fields

Code:

CREATEDDATE datetime not null

whereas the Oracle create DDL maps the same types to TIMESTAMP SQL fields

Code:

CREATEDDATE timestamp not null

I want MySQL to use timestamp as well. This mapping appears to be defined in the org.hibernate.dialect.MySQLDialect and org.hibernate.dialect.Oracle9Dialect classes, which contain

Code:

registerColumnType( Types.TIMESTAMP, "datetime" );

and

Code:

registerColumnType( Types.TIMESTAMP, "timestamp" );

respectively.

Is there a way of overriding these default mapping types, so that MySQL will use a SQL TIMESTAMP for hibernate calendar types, and probably SQL DATETIME for hibernate timestamp types (or java.util.Date)?

Cameron McKenzie · **Posted:** Tue Sep 08, 2009 10:45 am

Quote:

DATE vs. TIME vs. TIMESTAMP

It's noteworthy to point out how the registrationDate column, which is annotated to be TemporalType.DATE, simply gets a year-month-day value, whereas the lastAccessTime column is populated with a full timestamp, including both the day and the time (TemporalType.TIME is the third option which would have simply saved the time, and not the calendar day). By the way, TemporalType.TIMESTAMP is the default if it isn't otherwise specified in your code.

You can read more about column mapping here:

http://jpa.ezhibernate.com/Javacode/lea ... ingwithjpa