changing foreign key name

rbfree · #1 (**permalink**) 03-30-09, 19:06

Is there a long-term problem I'm not seeing with using one name for a foreign key in a child table that references a key by another name in the parent?

eg.

Code:

CREATE TABLE equipment_standstreated
(
    equipmenttypeID          INTEGER     NOT NULL
    standtreatedID             INTEGER     NOT NULL
,   PRIMARY KEY (equipmenttypeID, standtreatedID)
,   CONSTRAINT equipmenttypeID_fk
        FOREIGN KEY equipmenttypeID
            REFERENCES equipmenttypes (equipmenttypeID)
,   CONSTRAINT standstreatedID_fk
        FOREIGN KEY standstreatedID
           REFERENCES standstreated (standsID)  
);

r937 · #2 (**permalink**) 03-31-09, 12:18

not sure i understand your question, but the above syntax is wrong

you can use whatever name you want for the foreign key, i.e. standstreatedID is perfectly okay when referencing standsID in standstreated

the syntax error is due to the missing parentheses

Code:

CREATE TABLE equipment_standstreated
(
    equipmenttypeID          INTEGER     NOT NULL
    standtreatedID             INTEGER     NOT NULL
,   PRIMARY KEY (equipmenttypeID, standtreatedID)
,   CONSTRAINT equipmenttypeID_fk
        FOREIGN KEY ( equipmenttypeID )
            REFERENCES equipmenttypes (equipmenttypeID)
,   CONSTRAINT standstreatedID_fk
        FOREIGN KEY ( standstreatedID )
           REFERENCES standstreated (standsID)  
);

rbfree · #3 (**permalink**) 03-31-09, 14:20

Thanks R,

That does answer my question. My apologies for the syntax error; my sloppiness.

Internet Services

Web Development

Digital Marketing

Consumer Tech