That has been fixed in 1.7.0-SNAPSHOT. It was a bug.
Workaround: either, start using 1.7.0-SNAPSHOT (it is pretty stable) or overwrite the wrong template definition in templates::OracleDDL::foreignKeyColumn and templates::OracleDDL::uniManyForeignKeyColumn.
/Patrik
Patrik Nordwall wrote:
(re-posting this on behalf of Abhilash, since the question was hidden inside another thread)
Hi All,
I am using sculptor 1.6 and am facing some issues with the DDL Generation.
I am using the "inverse" relation between two entities. My database type is defined via db.product=oracle.
Now, here is the problem. In the generated ddl for oracle, I am getting the resultant ddl as
CREATE TABLE PERSON (
ID NUMBER(20) NOT NULL,
ENTITYID VARCHAR2(100) NOT NULL,
FIRSTNAME VARCHAR2(100),
CONTACT_INDEX INTEGER(10),
CLIENT NUMBER(20)
);
Running this in Oracle leads to problem, as the integer field doesn’t have a length.
Is there a way to overcome this problem?
I have given the following values in the sculptor-generator
db.oracle.type.PositiveInteger=NUMBER
db.oracle.type.Integer=NUMBER
db.oracle.type.Number=NUMBER
db.oracle.length.Integer=10
db.oracle.type.int=NUMBER
db.oracle.type.BigInteger=NUMBER
db.oracle.type.discriminatorType.INTEGER=NUMBER
db.oracle.length.discriminatorType.INTEGER=5
Regards
Abhilash
-------------------------
