From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Peter Fein <pfein(at)pobox(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Preventing Multiple Inheritance |
Date: | 2005-06-04 02:43:25 |
Message-ID: | 20050604024325.GA21354@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jun 03, 2005 at 16:04:26 -0500,
Peter Fein <pfein(at)pobox(dot)com> wrote:
>
> Ok, this makes a lot of sense & is just cleaner. Would you continue to
> do it this way if there were around a dozen derived tables (most with
> one or two columns)? I remember reading somewhere (perhaps the PG
> docs?) that a table with most of its columns NULL was a sign of
> misdesign as well... FWIW, most of the columns are small - varchar,
> ints, an array or two.
That may be bordering on a religious debate. There are people that say
you shouldn't have NULLs and should use an extra table instead.
I think for most people it is a matter of what will be easier to understand
and to some extent what is more efficient, that should dictate the design.
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Christian Ottersen | 2005-06-04 08:53:46 | How do I reinstall libeay32.dll |
Previous Message | Russell Smith | 2005-06-04 00:35:44 | Re: Old problem needs solution |