From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Andrew Perrin <clists(at)perrin(dot)socsci(dot)unc(dot)edu>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: "Best practice" advice |
Date: | 2003-01-17 20:16:18 |
Message-ID: | 200301171216.18219.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Andrew,
> The relationship is one-to-many, and I can handle that fine. The issue
> is: some of the references in the core documents will be to other core
> documents. Other references will be to documents that are not in the core
> documents table. I need to track whether the document referred to is
> in the core table or not. The question is how best to capture this. Ideas
> I have are:
I'd suggest, instead, having just one "documents" table with a boolean column
called "is_core". This will simplify relating core docs to each other, and
additionally allow for the promotion of "peripheral" docs to the core easily.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2003-01-17 20:43:31 | Re: double precision to numeric overflow error |
Previous Message | Andrew Perrin | 2003-01-17 20:06:20 | "Best practice" advice |