Re: relational db design question
From: mAsterdam <mAsterdam_at_vrijdag.org>
Date: Fri, 09 Feb 2007 00:46:37 +0100
Message-ID: <45cbb667$0$323$e4fe514c_at_news.xs4all.nl>
Date: Fri, 09 Feb 2007 00:46:37 +0100
Message-ID: <45cbb667$0$323$e4fe514c_at_news.xs4all.nl>
Evan Keel wrote:
> ... You are correct in making Magazine, Book, etc subtypes
> of Reference, at least at the logical level.
You don't know what the OP wants to accomplish
with his database. Is it relevant to the users of the
database to distinguish between types of references?
It depends on that.
Can we tell every type of reference in advance?
SMS, email, usenetposting - how to reference that? NNTP or google?
> You can implement this in three
> ways:
>
> - one big table allowing nulls
> - many subtype tables
> - a supertype/subtype tables with discriminator
>
> Google "implementing subtypes".
Or, without complete subtyping, two columns: protocol, locator Received on Fri Feb 09 2007 - 00:46:37 CET