Max,
Unfortunately DataDirect drivers for Oracle work the same as the ojdbc14.jar driver. They marshall the TIMESTAMP(6) oracle type to java.io.Serializable when reverse engineering. I would be will to look into creating the patch you are suggesting. Could you be more specific as to the requirements?

Thanks
Jerry

ReverseEngineeringStrategy, OverrideRepository and OverrideBinder is where most of the magic around this happens. JDBCReader and JDBCBinder is the one actually doing the reverse engineering.

what is needed is that the reverse engineering gets the notion of a native database type as an addition to how the resulting type is selected.


They do the matching against a reverse engineered column to the relevant hibernate type. This would need to get an additional parameter when looking up - and the one with the best match wins.

The biggest issue is that we don't have a good place to put the reverse engineerd native type since if we place it on the column it will leak into the generated templates where it will be redundant and not always apropriate to list it. Thus there need to be some additonal column info stored somewhere.