| From: | "David Johnston" <polobo(at)yahoo(dot)com> |
|---|---|
| To: | "'erhaminus'" <erhaminus(at)o2(dot)pl>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Composite type, DEFAULT, NOT NULL, REFERENCES |
| Date: | 2011-10-19 16:10:46 |
| Message-ID: | 030301cc8e79$a9b57410$fd205c30$@yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of erhaminus
Sent: Wednesday, October 19, 2011 10:33 AM
To: pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] Composite type, DEFAULT, NOT NULL, REFERENCES
Hi,
Is a way to define DEFAULT, NOT NULL and REFERENCES for members of composite type?
--------------------/Original Message---------------
The only way to constrain a Type is to use a DOMAIN but whether you can domain a composite type I do not know.
There is no concept of "Foreign Key" when it comes to Types, only Tables.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2011-10-19 16:19:57 | Re: Composite type, DEFAULT, NOT NULL, REFERENCES |
| Previous Message | erhaminus | 2011-10-19 14:32:50 | Composite type, DEFAULT, NOT NULL, REFERENCES |