From: | "John M(dot) Flinchbaugh" <glynis(at)butterfly(dot)hjsoft(dot)com> |
---|---|
To: | pgsql-sql(at)postgreSQL(dot)org |
Subject: | Re: [SQL] arrays |
Date: | 1999-12-04 14:02:13 |
Message-ID: | Pine.LNX.4.21.9912040855550.26133-100000@butterfly.hjsoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Sat, 4 Dec 1999, Stephen Davies wrote:
> Arrays do have a role in life: even in a "proper relational" world.
> The classical examples are publications with multiple authors, ISBns,
> subjects, keywords etc.
> Trying to fully normalise attributes like these leads to nonsensical and
> unusable database designs.
sorry, that is incorrect. in a proper system, you don't run out of
``slots''. say you give each publication an array to hold 3
authors. what happens when that 4th author comes along, then a
fifth? you always have a +1 problem. your database design will stand the
test of time better if you keep a good design.
one may say, ``just put 100 slots for authors''. then you are just
wasting space. if you normalize it (in this case store a table containing
the association between a publication and an author), you never hit an
upper limit, and you don't waste space in all those publication tables.
____________________}John Flinchbaugh{______________________
| -> glynis(at)hjsoft(dot)com <- john(at)cs(dot)millersv(dot)edu |
| glynis(at)netrax(dot)net http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~
From | Date | Subject | |
---|---|---|---|
Next Message | neko | 1999-12-04 15:05:26 | Re: [SQL] arrays |
Previous Message | Stephen Davies | 1999-12-04 09:31:58 | Re: [SQL] arrays |