db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Watzek <mwa.t...@spree.de>
Subject Re: ALTER TABLE clauses in TCK schemas
Date Tue, 26 Jul 2005 14:31:52 GMT
Hi Michelle,

I just noticed that the foreign key names in the "ALTER TABLE" 
statements below are used in the orm meta data. For this reason, I 
suggest to keep the "ALTER TABLE" statements and instead drop the 
REFERENCE clauses in the column defintions below.

Regards,
Michael

> Hi Michelle,
> 
> the TCK schemas for application identity and datastore indentity both 
> contain two "ALTER TABLE" statements on table "project_reviewer". I 
> think, both statements are redundant, because in the "CREATE TABLE" 
> statement of table "project_reviewer" column "PROJID" as well as column 
> "REVIEWER" have "REFERENCE" clauses already:
> 
> CREATE TABLE project_reviewer (
>     PROJID INTEGER REFERENCES projects NOT NULL,
>     REVIEWER INTEGER REFERENCES persons NOT NULL
> );
> 
> ALTER TABLE project_reviewer
>     ADD CONSTRAINT PR_PROJ_FK FOREIGN KEY
>         (PROJID) REFERENCES projects(PROJID);
> 
> ALTER TABLE project_reviewer
>     ADD CONSTRAINT PR_REV_FK FOREIGN KEY
>         (REVIEWER) REFERENCES persons(PERSONID);
> 
> For this reason, I suggest to delete both "ALTER TABLE" statements.
> 
> Regards,
> Michael


-- 
-------------------------------------------------------------------
Michael Watzek                  Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de        Buelowstr. 66
Tel.:  ++49/30/235 520 36       10783 Berlin - Germany
Fax.:  ++49/30/217 520 12       http://www.spree.de/
-------------------------------------------------------------------

Mime
View raw message