Add type in hbm.xml different than in .java

rodrigo.avila · **Joined:** Thu Aug 16, 2007 2:25 pm **Posts:** 5

Hibernate version:
3.2

Name and version of the database you are using:
PostgreSQL 8.1

When I generate code using Hibernate Tools, I need to use the following types for TIMESTAMP columns:

a) Use org.joda.time.contrib.hibernate.PersistentDateTime in the .hbm.xml file (this class persists org.joda.time.DateTime in timestamp columns)

b) Use the org.joda.time.DateTime in the .java file

How I do it automatically using Reverse Engineering? I think in use an ReverseEngineeringStrategy to do this, but I don't know how.

max · **Posted:** Sun Oct 07, 2007 5:16 am

You just need to inform hibernate tools during reverse engineering that when it sees a TIMESTAMP use the PersistentDateTime type; then when hbm2java runs it will consult PerstentDateTime (remember to have it in the classpath!) on which java type it should use (via the getReturnedClass() method)

so there is two options for this:

a) in a .reveng.xml file:

Code:

<type-mapping>
 <sql-type jdbc-type="TIMESTAMP" hibernate-type="org.joda.time.contrib.hibernate.PersistentDateTime"/>
</type-mapping>

b) via custom reveng strategy where you implement something like:

Code:

public class CustomStrategy extends DelegatingReverseEngineeringStrategy {
   
   
   public CustomStrategy(ReverseEngineeringStrategy res) {
      super(res);
   }

        public String columnToHibernateTypeName(TableIdentifier table, String columnName, int sqlType, int length, int precision, int scale, boolean nullable, boolean generatedIdentifier) {
                 if(sqlType==Types.TIMESTAMP) {
                          return "org.joda.time.contrib.hibernate.PersistentDateTime";
                    }    else {
              super.columnToHibernateTypeName(...);
}
   }

burnt · **Joined:** Mon Dec 17, 2007 11:50 am **Posts:** 14

Hi!
I have a similar problem. Can such a mapping be performed with annotations?

Thanks!

max · **Posted:** Tue Dec 18, 2007 12:19 pm

yes - but not sure if our code generation for hbiernate annotations spits out the custom type correctly. If not - a patch is very welcome ;)