New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exporting from schema with foreign key reference to another schema produces invalid code #211

Closed
jvmakine opened this Issue Aug 10, 2012 · 1 comment

Comments

Projects
None yet
2 participants
@jvmakine

Hi,

Using QueryDSL 2.7.2 and Oracle 10g express edition, I get references to missing classes when I try to export a Java model from schema containing foreign key references to another schema.

So, if I have a schema A with table

CREATE TABLE "A"."TABLEA" (
    "ID"    NUMBER(16,0) NOT NULL
)

and a schema B with table

CREATE TABLE "B"."TABLEB" (
    "ID"    NUMBER(16,0) NOT NULL,
    "A_ID"    NUMBER(16,0) NOT NULL,
    CONSTRAINT "FK_B" FOREIGN KEY ("A_ID") REFERENCES "A"."TABLE_A" ("ID")
)

and I try to export schema B with com.mysema.query.sql.codegen.MetaDataExporter, the generated code refers to class QTablea even though no such class is generated.

Maybe foreign key constraints to different schemas should be left out of the code generation?

Regards,
Juho

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Sep 10, 2012

Member

Released in 2.7.3

Member

timowest commented Sep 10, 2012

Released in 2.7.3

@timowest timowest closed this Sep 10, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment