| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SET NULL / SET NOT NULL |
| Date: | 2002-03-26 04:38:44 |
| Message-ID: | 13829.1017117524@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> What about temporary tables - is there any reason they shouldn't be able to
> modify a temporary table?
I don't see one.
> What about indices? Will twiddling the nullability break indices on a table
> in any way?
No, not as long as you aren't changing existing data in the table.
> And foreign keys - foreign keys only have to reference UNIQUE, right? The
> nullability isn't an issue?
Not sure about that --- Stephan or Jan will know.
> Lastly - in a multicolumn primary key, does EVERY column in the key need to
> be NOT NULL?
Yes, I believe so.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-03-26 04:44:26 | Re: Rolling v7.2.1 ... |
| Previous Message | Christopher Kings-Lynne | 2002-03-26 04:33:33 | Re: SET NULL / SET NOT NULL |