Type mapping during Reverse Engineering ignored

mario ulmer · **Joined:** Thu Nov 13, 2008 8:21 am **Posts:** 8

I try to reverse engineer JPA entity classes from a Oracle 10g schema with the following hibernate.revenge.xml

Code:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-reverse-engineering PUBLIC "-//Hibernate/Hibernate Reverse Engineering DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" >

<hibernate-reverse-engineering>
  <schema-selection match-schema="CRDE_ERFASSUNG" match-table="LS_LDP_.*" />
  <type-mapping>
    <sql-type jdbc-type="NUMERIC" precision="32" not-null="false" hibernate-type="java.lang.Long" />
    <sql-type jdbc-type="NUMERIC" precision="1" hibernate-type="java.lang.Byte" />
  </type-mapping>
</hibernate-reverse-engineering>

The appropriate DB columns are looking like this for instance

Code:

SATZ_ID|NUMBER(32,0)|NOT NULL|PK

Code:

RELATION_ART_ANF_CODE|NUMBER(1,0)|NULL

I know that in case of satz_id the precision will be gone but this is different chapter :-)

The classes are generated properly but without the declared type mapping.

Am I doing something wrong?

I'm a using Eclipse 3.3.2, Hibernate-Core 3.2.2.Beta1, Oracle10g, ojdbc14.jar, JDK 1.5.0_14

Mario

max · **Posted:** Wed Nov 19, 2008 7:12 am

I think to recall that Oracle does not map NUMBER to java.sql.type.Types.NUMERIC but something else.

Look in the logs to see what is actually being reported.

mario ulmer · **Joined:** Thu Nov 13, 2008 8:21 am **Posts:** 8

Ok, I agree.

If I try to change now from

Code:

<sql-type jdbc-type="NUMERIC" precision="32" not-null="false" hibernate-type="java.lang.Long" /> 

to

Code:

<sql-type jdbc-type="NUMBER" precision="32" not-null="false" hibernate-type="java.lang.Long" /> 

I get the following error

Code:

org.hibernate.MappingException: jdbc-type: NUMBER is not a known JDBC Type nor a valid number

Which jdbc-type is compatibel to SQL NUMBER(32,0) and will be identified properly?

Mario

max · **Posted:** Thu Nov 20, 2008 10:15 am

i dont have a oracle installation with me right now.

enable debug logging and the logs should tell you which type it is actually looking up for.

mario ulmer · **Joined:** Thu Nov 13, 2008 8:21 am **Posts:** 8

The solution is:

Code:

<type-mapping>
    <sql-type jdbc-type="DECIMAL" precision="32" not-null="true" hibernate-type="java.lang.Long" />
    <sql-type jdbc-type="DECIMAL" precision="1" hibernate-type="java.lang.Byte" />
</type-mapping>

The second mistake was the value for the attribute not-null="false" in the first line which should be "true" instead.

This works fine for my problem.

Thx for the support!

Mario