[ https://issues.apache.org/jira/browse/IBATIS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507925 ]
Jeff Butler commented on IBATIS-443: ------------------------------------ I think the best approach is to implement your own JavaTypeResolver. You can subclass JavaTypeResolverDefaultImpl and override the "initializeResolvedJavaType" method something like this: try { super.initializeResolvedJavaType(cd); } catch (UnsupportedDataTypeException e) { // deal with Oracle's wierdness here. } Too bad Oracle doesn't use Types.OTHER for these kinds of things - that's what it's there for! But no one ever claimed that Oracle was interested in following standards. Also, in the future, please use the mailing lists for support requests. > abator, unsupported data type for oracle "timestamp with timezone" > ------------------------------------------------------------------ > > Key: IBATIS-443 > URL: https://issues.apache.org/jira/browse/IBATIS-443 > Project: iBatis for Java > Issue Type: Improvement > Environment: abator > Reporter: THURNER rupert > > is there any good possibility to support proprietory datatypes in abator? > i.e. "timestamp with timezone"? currently abator fails to generate artefacts > with error message "unsupported data type, column ignored". > we know this is no problem if you do not have 50 tables with 3 timestamp > columns each, and a quite fixed db schema :) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.