| From: | "Kevin McCarthy" <kemccarthy1(at)gmail(dot)com> |
|---|---|
| To: | pgsql-novice(at)postgresql(dot)org |
| Subject: | foreign key constraint to multiple tables |
| Date: | 2007-08-13 16:14:28 |
| Message-ID: | 4178da10708130914x1f5b0304p21f4ed63f08c7fb5@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
I have a table with a column that will join with one of several tables based
on the value of another column. I'm not sure if this column can be set as a
foreign key to any of these tables, may be simply bad design on my part. The
item_type_id column of a record of 'A' will reference one of the 'type'
table records depending upon what the value of the record's item_type column
is.
Is there a way to set the item_type_id column in Table A as a foreign key to
the other tables depending? Or would there be a better way to design this
schema?
TIA
CREATE TABLE ABC(
id SERIAL PRIMARY KEY,
item_type character varying(10) NOT NULL,
item_type_id INTEGER
);
CREATE TABLE typeA(
typeA_id SERIAL PRIMARY KEY
);
CREATE TABLE typeB(
typeB_id SERIAL PRIMARY KEY
);
CREATE TABLE typeC(
typeC_id SERIAL PRIMARY KEY
);
--
Kevin McCarthy
kemccarthy1(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jasbinder Singh Bali | 2007-08-13 16:50:20 | Postmaster start up problems (can't create lock file ) |
| Previous Message | Tom Lane | 2007-08-13 13:37:20 | Re: [NOVICE] Install two different versions of postgres which should run in parallel |