Skip site navigation (1) Skip section navigation (2)

One Text Table or Multiple Text Tables - Design Tradeoffs?

From: Bryan Emrys <bryan(dot)emrys(at)gmail(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Subject: One Text Table or Multiple Text Tables - Design Tradeoffs?
Date: 2008-06-10 13:07:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-sql
(Trying to start a new thread instead of my accidental intrusion into another thread)

Hello Everyone, 

In a text-heavy database, I'm trying to make an initial design decision in the following context. 

There is a lot of long text that I could break down into three different categories:
        a. Laws 
                i. Only 1 country per law, many laws
                ii. There are multiple types of laws (statutes, regulations, court cases, proposed laws, etc)
                iii. Each law will have only one type
                iv. Each law may refer to many other laws
        b. Treaties 
                i. 2 countries per treaty
                ii. At any one time, there will only be one treaty in force between any two countries
                iii. There may be proposed new treaties which will supercede old treaties when finally ratified
        c. Commentary 
                i. Any commentary could refer to one or more laws or treaties
                ii. Any commentary may have one or more authors
                iii. Any commentary may refer to one or more countries

The conceptual question is what are the trade-offs between having one textual table compared with multiple text tables? Any help on pointing out practical considerations would be appreciated.




pgsql-sql by date

Next:From: Shavonne Marietta WijesingheDate: 2008-06-10 13:14:31
Subject: Re: Nextval & Currval
Previous:From: Bryan EmrysDate: 2008-06-10 13:04:43
Subject: Apologies to the list. Please ignore accidental thread intrusion

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group