From: | "Sean Davis" <sdavis2(at)mail(dot)nih(dot)gov> |
---|---|
To: | "plu tard" <plutard12(at)hotmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: users table and user_details table? Bad form? |
Date: | 2007-11-28 12:42:46 |
Message-ID: | 264855a00711280442gaab2601u8cfd44a9a27f1e18@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Nov 28, 2007 1:37 AM, plu tard <plutard12(at)hotmail(dot)com> wrote:
> I have a users table that's getting pretty large (~ 2M rows) and that's
> very sparse, because most users register but don't do much, so a lot
> of the columns are NULL.
>
> I'm thinking of adding a user_details table with a unique foreign key
> constraint to the users table, and moving all those rarely populated
> columns into it. A row in user_details would only be created it we need
> to populate one or more of the columns in there.
>
> Is that an okay idea?
>
> It doesn't violate any normalization rules, does it?
> And in practice, does it cause any problems?
>
That sounds like a good idea.
Sean
From | Date | Subject | |
---|---|---|---|
Next Message | Wright, George | 2007-11-28 16:27:07 | time duration |
Previous Message | plu tard | 2007-11-28 06:37:25 | users table and user_details table? Bad form? |