From: Josh Berkus <josh@agliodbs.com>
To: Andrew Perrin <clists@perrin.socsci.unc.edu>
To: pgsql-sql@postgresql.org
Subject: Re: "Best practice" advice
Date: Fri, 17 Jan 2003 12:16:18 -0800
Message-ID: <200301171216.18219.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0301171459350.16506-100000@perrin.socsci.unc.edu>
References: <Pine.LNX.4.21.0301171459350.16506-100000@perrin.socsci.unc.edu>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, clists@perrin.socsci.unc.edu
Subject: Re: "Best practice" advice
In-Reply-To: <200301171216.18219.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox