I generated the database using an sql script. Here is a snippet of that
script for the ARC table. The behavior is not specific to this table. It
occurs in all the generated DDL.
CREATE TABLE Arc (
ID INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY,
Edge INTEGER DEFAULT 0,
Product INTEGER DEFAULT 0,
Priority INTEGER DEFAULT 1,
PRIMARY KEY (ID));
/* Foreign keys for Arc */
ALTER TABLE Arc ADD CONSTRAINT EdgeArc FOREIGN KEY (Edge) REFERENCES Edge
(ID);
ALTER TABLE Arc ADD CONSTRAINT ProductArc FOREIGN KEY (Product) REFERENCES
Product (ID);
So, notice that in my original SQL the constraints are named (e.g 'EdgeArc')
The Keys.java class seems to have captured the names.
//
-------------------------------------------------------------------------
// FOREIGN KEY definitions
//
-------------------------------------------------------------------------
public static final ForeignKey<ArcRecord, EdgeRecord> EDGEARC =
ForeignKeys0.EDGEARC;
public static final ForeignKey<ArcRecord, ProductRecord> PRODUCTARC =
ForeignKeys0.PRODUCTARC;
However, the DDL generated statements are like this:
create table "APP"."ARC"(
"ID" integer not null,
"EDGE" integer,
"PRODUCT" integer,
"PRIORITY" integer,
constraint "SQL171126155154580"
primary key ("ID")
)
alter table "APP"."ARC"
add constraint
foreign key ("EDGE")
references "EDGE" ("ID")
alter table "APP"."ARC"
add constraint
foreign key ("PRODUCT")
references "PRODUCT" ("ID")
So that the generated DDL are missing the constraint names.
BTW, my intent is to use the generated DDL to essentially replicate the
database and restore the original schema, which is one of the use cases for
the DDL functionality. In the jOOQ manual, the generated alter statements
do have the names for the constraints. So, I don't see what is going on
here.
On Tuesday, November 28, 2017 at 5:53:34 AM UTC-6, Lukas Eder wrote:
>
> Hi Manuel,
>
> Thank you very much for your message.
>
> In the generated SQL, there's a double whitespace, which seems to indicate
> that the name of your constraint was simply empty (""). I wonder why that
> is. Are the names registered correctly in the generated Keys.java class?
> Can you share the constraint definition here?
>
> Thanks,
> Lukas
>
> 2017-11-26 23:30 GMT+01:00 Manuel Rossetti <[email protected]
> <javascript:>>:
>
>> I believe that there is a problem with how the DDL statements are being
>> constructed. I would like to know if anyone else sees this as a problem.
>>
>> DSLContext create = DSL.using(getConnection(), SQLDialect.DERBY);
>>
>> Queries queries = create.ddl(getUserSchema());
>>
>> The "ALTER" queries do not have their constraints named. In the exception
>> below, the name of the constraint is expected but the keyword "foreign" was
>> encountered. In the original creation script for the database all
>> constraints were named but the name 'EdgeArc' was not captured by the
>> create.ddl() statement.
>>
>> ALTER TABLE Arc ADD CONSTRAINT EdgeArc FOREIGN KEY (Edge) REFERENCES Edge
>> (ID);
>>
>> SQLException when executing alter table "APP"."ARC" add constraint
>> foreign key ("EDGE") references "EDGE" ("ID")
>> java.sql.SQLSyntaxErrorException: Syntax error: Encountered "foreign" at
>> line 1, column 41.
>> at
>> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
>> Source)
>> at
>> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
>>
>> Source)
>> at
>> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
>> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
>> at
>> dbtools.dbutil.EmbeddedDerbyDatabase.executeCommand(EmbeddedDerbyDatabase.java:680)
>> at
>> dbtools.dbutil.EmbeddedDerbyDatabase.executeCommands(EmbeddedDerbyDatabase.java:710)
>> at
>> dbtools.dbutil.EmbeddedDerbyDatabase.duplicate(EmbeddedDerbyDatabase.java:210)
>> at
>> dbtools.dbutil.EmbeddedDerbyDatabase.testWrting(EmbeddedDerbyDatabase.java:910)
>> at
>> dbtools.dbutil.EmbeddedDerbyDatabase.main(EmbeddedDerbyDatabase.java:882)
>> Caused by: ERROR 42X01: Syntax error: Encountered "foreign" at line 1,
>> column 41.
>> at org.apache.derby.iapi.error.StandardException.newException(Unknown
>> Source)
>> at org.apache.derby.iapi.error.StandardException.newException(Unknown
>> Source)
>> at
>> org.apache.derby.impl.sql.compile.ParserImpl.parseStatementOrSearchCondition(Unknown
>>
>> Source)
>> at
>> org.apache.derby.impl.sql.compile.ParserImpl.parseStatement(Unknown Source)
>> at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown
>> Source)
>> at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source)
>> at
>> org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown
>>
>> Source)
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "jOOQ User Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
