| From: | ljb <lbayuk(at)mindspring(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Match Full on foreign Key |
| Date: | 2003-02-09 22:57:23 |
| Message-ID: | b26mci$2sj7$1@news.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | elein | 2003-02-10 00:36:06 | Re: PostgreSQL Mailing Lists in Italian? |
| Previous Message | Lee Harr | 2003-02-09 22:56:23 | Re: PostgreSQL x Oracle |