You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by "Lustig, Marc (Allianz Deutschland, externer Mitarbeiter)" <EX...@allianz.de> on 2008/11/14 10:53:07 UTC
Continnum 1.2.2 doesn't work with Oracle
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.
Re: Continnum 1.2.2 doesn't work with Oracle
Posted by Emmanuel Venisse <em...@gmail.com>.
It isn't possible to use hibernate at ASF due to the Hibernate license
Emmanuel
On Fri, Nov 14, 2008 at 4:29 PM, Lustig, Marc (Allianz Deutschland, externer
Mitarbeiter) <EX...@allianz.de> wrote:
> 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:emmanuel.venisse@gmail.com]
> Gesendet: Freitag, 14. November 2008 14:11
> An: users@continuum.apache.org
> 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) <EX...@allianz.de> 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.
> >
>
AW: Continnum 1.2.2 doesn't work with Oracle
Posted by "Lustig, Marc (Allianz Deutschland, externer Mitarbeiter)" <EX...@allianz.de>.
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:emmanuel.venisse@gmail.com]
Gesendet: Freitag, 14. November 2008 14:11
An: users@continuum.apache.org
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) <EX...@allianz.de> 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.
>
AW: Continnum 1.2.2 doesn't work with Oracle
Posted by "Lustig, Marc (Allianz Deutschland, externer Mitarbeiter)" <EX...@allianz.de>.
Bonsoir Emmanuel,
I wasn't aware about the license issue with Hibernate.
By default, package-mssql.orm is included in continuum-model-x.jar at /, so this would mean MSSQL would be the default database for Continuum, which isn't the case.
And even I deleted this file and added my package-oracle.orm to the jar, without any effect.
So, I suppose, there is something action needed in order to register the file for JPOX JDO-layer.
Marc
-----Ursprüngliche Nachricht-----
Von: Emmanuel Venisse [mailto:emmanuel.venisse@gmail.com]
Gesendet: Freitag, 14. November 2008 17:54
An: users@continuum.apache.org
Betreff: Re: Continnum 1.2.2 doesn't work with Oracle
jpox select it automatically if it find it in the classpath
Emmanuel
On Fri, Nov 14, 2008 at 3:53 PM, Lustig, Marc (Allianz Deutschland, externer
Mitarbeiter) <EX...@allianz.de> wrote:
> ok, I created one. But where to set the DB-dialect to be used?
>
>
> -----Ursprüngliche Nachricht-----
> Von: Emmanuel Venisse [mailto:emmanuel.venisse@gmail.com]
> Gesendet: Freitag, 14. November 2008 14:11
> An: users@continuum.apache.org
> 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) <EX...@allianz.de> 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.
> >
>
Re: Continnum 1.2.2 doesn't work with Oracle
Posted by Emmanuel Venisse <em...@gmail.com>.
jpox select it automatically if it find it in the classpath
Emmanuel
On Fri, Nov 14, 2008 at 3:53 PM, Lustig, Marc (Allianz Deutschland, externer
Mitarbeiter) <EX...@allianz.de> wrote:
> ok, I created one. But where to set the DB-dialect to be used?
>
>
> -----Ursprüngliche Nachricht-----
> Von: Emmanuel Venisse [mailto:emmanuel.venisse@gmail.com]
> Gesendet: Freitag, 14. November 2008 14:11
> An: users@continuum.apache.org
> 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) <EX...@allianz.de> 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.
> >
>
AW: Continnum 1.2.2 doesn't work with Oracle
Posted by "Lustig, Marc (Allianz Deutschland, externer Mitarbeiter)" <EX...@allianz.de>.
ok, I created one. But where to set the DB-dialect to be used?
-----Ursprüngliche Nachricht-----
Von: Emmanuel Venisse [mailto:emmanuel.venisse@gmail.com]
Gesendet: Freitag, 14. November 2008 14:11
An: users@continuum.apache.org
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) <EX...@allianz.de> 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.
>
Re: Continnum 1.2.2 doesn't work with Oracle
Posted by Emmanuel Venisse <em...@gmail.com>.
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) <EX...@allianz.de> 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.
>