If it's not possible to define the dialect, then how to make use of any package-somedatabase.orm ? With hibernate, no such issues would exist....
-----Ursprüngliche Nachricht----- Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 14. November 2008 14:11 An: [email protected] Betreff: Re: Continnum 1.2.2 doesn't work with Oracle ok, you can overwrite length values by adding an orm file specific to Oracle in the classpath. We already have one for mssql [1] and it is packaged in continuum-model jar When you'll have one, can you create an issue in Jira and attach it so we'll can include it in next releases. Emmanuel [1] https://svn.apache.org/repos/asf/continuum/tags/continuum-1.2.2/continuum-model/src/main/resources/package-mssql.orm On Fri, Nov 14, 2008 at 10:53 AM, Lustig, Marc (Allianz Deutschland, externer Mitarbeiter) <[EMAIL PROTECTED]> wrote: > > > 2008-11-14 09:34:13,476 [main] ERROR JPOX.RDBMS - Error thrown executing > CREATE TABLE CHANGESET > ( > CHANGESET_ID NUMBER NOT NULL, > AUTHOR VARCHAR2(255) NULL, > CHANGECOMMENT VARCHAR2(8192) NULL, > CHANGEDATE NUMBER NOT NULL, > ID VARCHAR2(255) NULL, > MODEL_ENCODING VARCHAR2(255) NULL, > CHANGES_SCMRESULT_ID_OID NUMBER NULL, > CHANGES_INTEGER_IDX NUMBER(10) NULL > ) : ORA-00910: specified length too long for its datatype > > java.sql.SQLSyntaxErrorException: ORA-00910: specified length too long for > its datatype > > > --> for Oracle, VARCHAR2 max size is 4000 > > I was unable to find the JDO entity-definition in the continuum webapp. > > Please give a hint for the quick-fix. >
