This is an error in Abator. There should, absolutely, be a way for you to use the columnOverride and not have to redefine your columns. I'll fix it.
Jeff Butler On Thu, Mar 27, 2008 at 5:28 PM, Jesse Reimann <[EMAIL PROTECTED]> wrote: > I'm using the Oracle datatype "TIMESTAMP WITH TIME ZONE" in my database > and when using Abator I get the following error > > > > "Unsupported Data Type in table TEST.CALL_DATA_DETAIL, column: > INITIATION_DATE, column ignored" > > > > I tried setting up a columnOveride for it since I am just going to map it > to a java.util.Date and use the Timestamp JDBC type however it seems that > my columnOveride is not valid because the column has been ignored. > > > > I have found a workaround which is to change my TIMESTAMP WITH TIME ZONE > columns to just TIMESTAMP in my DB and then run Abator for the code > generation and then revert the DB columns back to "TIMESTAMP WITH TIME ZONE" > since the generated code will work fine with either database column > definition. > > > > Is there some other way to resolve this so I don't have to modify my > database column definitions every time I need to regenerate my code with > Abator? > > > > Thanks, > > > > Jesse Reimann > > >
