Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 9FCDB477459 for ; Fri, 17 Jan 2003 15:15:43 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 03635477362 for ; Fri, 17 Jan 2003 15:14:08 -0500 (EST) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2317610; Fri, 17 Jan 2003 12:14:11 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Andrew Perrin , pgsql-sql@postgresql.org Subject: Re: "Best practice" advice Date: Fri, 17 Jan 2003 12:16:18 -0800 X-Mailer: KMail [version 1.4] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301171216.18219.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/280 X-Sequence-Number: 11145 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 colu= mn=20 called "is_core". This will simplify relating core docs to each other, an= d=20 additionally allow for the promotion of "peripheral" docs to the core easil= y. --=20 -Josh Berkus Aglio Database Solutions San Francisco