Oracle TIMESTAMP and BLOB return OTHER in reveng config

caterham · **Posted:** Thu Mar 02, 2006 8:40 am

Hi,

it's me again. I'm working with Oracle 10g and noticed that the TIMESTAMP data type and BLOB is returned as OTHER in the reverse engineering config. I tried to differ both fields with length, scale or precision, but as soon as I have two JDBC types "OTHER" in my hibernate.reveng.xml the data type in my Java class is java.io.Serializable and not the one specified in my reveng-file. If there is just one "OTHER" in my hibernate.reveng.xml it's correctly mappepd e.g. to java.util.Date; but of course I do not want BLOB mapped to java.util.Date.

Any workaround for this?

Rgds,
Axel

max · **Posted:** Thu Mar 02, 2006 8:57 am

hmmm....maybe a good usecase for me to actually add db-specific mappings.

how does your reveng.xml file look like ?

caterham · **Posted:** Thu Mar 02, 2006 9:21 am

max wrote:

how does your reveng.xml file look like ?

I can't reproduce the error any more that both types are mapped to java.io.Serializable. :-( Now both types are mapped to Date or Blob.

This is the working one which maps TIMESTAMP to java.util.Date but also BLOB to java.util.Date.

Code:

<hibernate-reverse-engineering>
<type-mapping>
   <sql-type jdbc-type="TIMESTAMP" hibernate-type="java.util.Date" />
   <sql-type jdbc-type="DATE" hibernate-type="java.util.Date" />
   <sql-type jdbc-type="TIME" hibernate-type="java.util.Date" />
   <sql-type jdbc-type="OTHER" hibernate-type="java.util.Date"
      not-null="false"/>
   <sql-type jdbc-type="CHAR" hibernate-type="java.lang.Boolean"
      length="1" />
   <sql-type jdbc-type="DECIMAL" hibernate-type="java.lang.Integer"
      not-null="true" precision="8" />
   <sql-type jdbc-type="DECIMAL" hibernate-type="java.lang.Long"
      not-null="true" precision="12" />
   <sql-type jdbc-type="DECIMAL" hibernate-type="java.lang.Long"
      precision="10" not-null="true" />
   <sql-type jdbc-type="DECIMAL" hibernate-type="java.lang.Long"
      precision="12" not-null="false" />
</type-mapping>
</hibernate-reverse-engineering>

If I add this

Code:

<sql-type jdbc-type="OTHER" hibernate-type="java.sql.Blob" not-null="false" length="4000"/>

it seems that the length attribute is ignored for "OTHER" types, which is comprehensible.

So the java.io.Serializable error seems to be my fault. If I can reproduce it again, I will post it here. But maybe you have an idea how to differ between two "OTHER" types.

Axel

max · **Posted:** Thu Mar 02, 2006 11:21 am

it very much depend what the driver returns for the values - try and enable logging and let me know ;)

caterham · **Posted:** Thu Mar 02, 2006 12:25 pm

Great, it seems to be a driver issue. I wondered that in my reveng strategy sqlType: 1111 was returned for both columns. Squirrel, my SQL client, showed the types correctly. I then replaced ojbc14.jar in my project with the one from my Squirrel directory. After I restarted eclipse the reveng xml editor showed the types correctly. I think generation will now work too. I hate Oracle for providing totaly different drivers with exactly the same name. :-(