From: | "Sebastian Ritter" <ritter(dot)sebastian(at)gmail(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Database normalization |
Date: | 2007-08-28 11:47:45 |
Message-ID: | 99b656cb0708280447x4eb7c45axec01c8d0ebc6c82d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hello,
>
> I have a fairly basic question about database design where im not sure
> which approach is considered correct.
>
> I have two different entities: Clients and Services. Both allow users to
> add progressive updates about the two entities.
>
> The update/message format is exactly the same for both. Should I make two
> different tables:
>
> client_updates and service_updates
> or
> one table with extra columns : is_client, client_id, service_id, where
> either client_id or service_id would be null depending on the is_client
> boolean?
>
> The major problem is simply relating the foreign key in the updates table
> back to the correct entity, client or service.
>
> Regards,
> Sebastian
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Glaesemann | 2007-08-28 13:00:42 | Re: fetch first rows of grouped data |
Previous Message | hubert depesz lubaczewski | 2007-08-28 09:14:21 | Re: fetch first rows of grouped data |