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 Wed, 27 Jul 2005 13:05:49 GMT
Hi Michelle,

that's fine. I noticed that datastoreidentity0.project_reviewer still 
contains a reference clause on column "REVIEWER". Is that on purpose?

Regards,
Michael

> Thanks for noticing this, Michael.  I will delete the REFERENCES part of 
> the CREATE TABLE statements.  I added the ALTER TABLE statements in 
> order to have a named constraint, so I want to keep those.
> 
> -- Michelle
> 
> Michael Watzek wrote:
> 
>> 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