I am using seam gen to reverse engineer an Oracle database with fileds of the TIMESTAMP(6) type. When I reverse engineer these tables it marshalls TIMESTAMP(6) to java.io.Serializable. After adding this type mapping node:

<hibernate-reverse-engineering>
<!-- Added by JEEads to take care of TIMESTAMP mapping issue 10/31/08 -->
<type-mapping>
<sql-type jdbc-type="TIMESTAMP" hibernate-type="java.sql.Timestamp" />
<sql-type jdbc-type="NUMERIC" hibernate-type="java.lang.Long" />
<sql-type jdbc-type="DECIMAL" hibernate-type="java.lang.Long" />
<sql-type jdbc-type="VARCHAR" length="1" not-null="true" hibernate-type="java.lang.Character" />
<sql-type jdbc-type="VARCHAR" length="1" hibernate-type="char" />
<sql-type jdbc-type="VARCHAR" hibernate-type="string" />
</type-mapping>


<!-- This file is intentionally generated empty by seam-gen -->
<!-- You can add any filtering/setup you want for your app -->

</hibernate-reverse-engineering>

the problem persisted. How do I need to type map the ORACLE TIMESTAMP(6) so it maps to java.sql.Timestamp?


Thanks
Jerry

Has anyone been able to solve this problem? I'm going through exactly the same thing, and the mapping file is not working in my case either.

I've even tried length="6", but no luck.

I found that oracle Timestamp maps to sql Other so what I did was change the generlated files so instead of Serializable the Timestamps map to Timestamp. It is a hassle but it works fine. Another issue I had was that many of the CMR's are mapped to Set rather than List which rich:dataTables and subTables cannot use. I changed those to List and they work fine.

Hope this helps.

Jerry

I have 70+ tables in my database and each table contains average 20-30 fields. If i have to change the datatypes manually it will take ages. I added the following lines in seam-gen.reveng.xml files.
<type-mapping>
<sql-type jdbc-type="TIMESTAMP" hibernate-type="date" length="9"/>
<sql-type jdbc-type="INTEGER" hibernate-type="java.Lang.Integer" />
<sql-type jdbc-type="NUMERIC" hibernate-type="java.Lang.Float" />
<sql-type jdbc-type="DECIMAL" hibernate-type="java.Lang.Double" />
<sql-type jdbc-type="VARCHAR" length="1" not-null="true" hibernate-type="java.lang.Character" />
<sql-type jdbc-type="VARCHAR" length="1" hibernate-type="char" />
<sql-type jdbc-type="VARCHAR" hibernate-type="string" />
</type-mapping>

Still Seam is generating Timestamp -> Serializable, INTEGER,NUMERIC,DECIMAL -> BigDecimal.

Can anyone assist?

What I ended up doing is making an Ant build task that runs right after the hibernate reverse-engineering task.
Its an Ant "replace task" that searches for 'type="serializable"' and replaces it with 'type="java.sql.Timestamp"'.
I could have used a more precise / complicated Ant replaceregex task to ensure I'm only replacing serializable where there's a TIMESTAMP, but I only have 'type="serializable"' where I was expecting 'type="java.sql.Timestamp"', so I'm not overwriting any unintentional fields.

How about using this:

<sql-type jdbc-type="OTHER" hibernate-type="java.sql.Timestamp" />

This works for me, because I only have oracle timestamp mapped to jdbc type other.

I don't know if this is Hibernate Tools bug or not? I hope to hear from Hibernate guys.

Tuno is right - that is the current "workaround"

To get it fully solved we shuold have a db-type or native-type to match on too so we can support drivers who doesn't support jdbc metadata typesystem fully.

Has this been resolved? I'm having the same issue and would like to use something better than a workaround that maps all unrecognized types to Timestamp.

unfortunately not. contributions welcome.