Re: N all-way relationship

Поиск
Список
Период
Сортировка
Искать
От
chester c young
Тема
Re: N all-way relationship
Дата
в 12:33:14
Msg-id
20030513163316.11749.qmail@web12708.mail.yahoo.com
Ответ на
Список
Дерево обсуждения
N all-way relationship "Ryan" <pgsql-sql@seahat.com>
Re: N all-way relationship chester c young <chestercyoung@yahoo.com>
Re: N all-way relationship Bruno Wolff III <bruno@wolff.to>
Re: N all-way relationship Jamie Lawrence <pgsql-sql@jal.org>
--- Ryan  wrote:
> This is largely related to cross referencing part numbers

Why not
table master_part(  part_id int primary key, part_no not null unique, ... );
table vendor( vendor_no primary key, ... );
table vendor_part( part_id int primary key default(seq), vendor_no references vendor, master_part references master_part( part_id ), vendor_part, constraint unique( vendor_no, vendor_part ), ... );

Everything here is nice and normal (use part_id to avoid compound
primary keys).  Then use views for all cross referencing.



__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com


В списке pgsql-sql по дате отправления
От: Adam Sherman
Дата:
От: Joachim Zauner
Дата:
Сообщение: See Temp Table from Trigger
FAQ