Re: Database design qn for one-to-many relationship

From: Jon Maz <jonmaz_at_surfeu.de.no.spam>
Date: Fri, 7 Mar 2003 16:55:52 +0100
Message-ID: <b4af9q$qft$1_at_news.online.de>


Thanks for the advice, Karl. As this project is already under way in SQL Server, an OODB is out, so it looks like I'm going to settle for having a good-looking RDB!

Cheers,

JON "karl wettin" <wettin_at_users.sourceforge.net> wrote in message news:20030305170356.5d9ed63e.wettin_at_users.sourceforge.net...

If you want your relation database to look and feel as object oriented as possible, be consistent and store attributes by them self and keep the links of any relation (association/superrelation) in one table per relation.

This is however not very speedy and will require multiple queries or joins to find the other end of any relation.

So your choises are speed or a good looking RDB. If you still can't make up your mind you might want to consider using an OODB.

karl Received on Fri Mar 07 2003 - 16:55:52 CET

Original text of this message