Re: Design for Category Feature

From: David Portas <REMOVE_BEFORE_REPLYING_dportas_at_acm.org>
Date: 14 Oct 2005 07:39:25 -0700
Message-ID: <1129300765.422742.41660_at_g44g2000cwa.googlegroups.com>

I don't understand what "CATEGORY_ID" is in your model. I would have expected to see this (SQL):

CREATE TABLE person_category (category_id INTEGER NOT NULL REFERENCES categories (category_id), person_id INTEGER NOT NULL REFERENCES persons (person_id), PRIMARY KEY (category_id,person_id));

Why would you need a third column?

-- 
David Portas 
SQL Server MVP 
--

Received on Fri Oct 14 2005 - 16:39:25 CEST

This message: [ Message body ]
Next message: Tony D: "Re: Flat Query"
Previous message: David Portas: "Re: Do we always have to update or insert? Why can't we just relate?"
In reply to: davidbryce_at_fastmail.fm: "Design for Category Feature"
Next in thread: davidbryce_at_fastmail.fm: "Re: Design for Category Feature"
Reply: davidbryce_at_fastmail.fm: "Re: Design for Category Feature"
Reply: vldm10: "Re: Design for Category Feature"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message