Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Match Full on foreign Key
- From: ljb <lbayuk(at)mindspring(dot)com>
- To: pgsql-general(at)postgresql(dot)org
- Subject: Re: Match Full on foreign Key
- Date: Sun, 9 Feb 2003 22:57:23 +0000 (UTC)
- Message-id: <b26mci$2sj7$1@news.hub.org> <text/plain>
sl26(at)ukc(dot)ac(dot)uk wrote: > I have defined the following foreign keys in a table: > > ********* > FOREIGN KEY (staff_login) REFERENCES staff (staff_login) MATCH FULL ON > DELETE CASCADE ON UPDATE CASCADE, > > FOREIGN KEY (module_code) REFERENCES module (module_code) MATCH FULL > ON DELETE CASCADE ON UPDATE CASCADE, > ********* > > these two fields make the primary key of the table in which they are > in. > > MATCH FULL will not allow one column of a multi-column foreign key to > be NULL unless all foreign key columns are NULL...so: >... MATCH FULL is not relevant because you don't have multi-column foreign keys. You have 2 single column foreign keys.
- References:
- Match Full on foreign Key
- From: Marc Richards
- Match Full on foreign Key
- Prev by Date: Re: PostgreSQL x Oracle
- Next by Date: configure: error: no acceptable C compiler found in $PATH
- Previous by thread: Match Full on foreign Key
- Next by thread: configure: error: no acceptable C compiler found in $PATH
- Indexes: