relationship/table design question

From: "Taylor Lewick" <tlewick(at)kc(dot)rr(dot)com>
To: <pgsql-sql(at)postgresql(dot)org>
Subject: relationship/table design question
Date: 2003-12-03 02:45:45
Message-ID: 001c01c3b947$8cf3cb70$c0341a41@taylor
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Hi all, new to postgresql and I have a question about how to lay out my
database.

I have a database with 4 main tables, organizations, contacts, events,
grants. My thinking here is that organizations can have contacts, sponsor
events,
and sponsor grants, so it is what I would call
the main table. I know how to set up the other tables so that they have a
reference back to org_id. (Basically a foreign key).

How would I handle it (set up in SQL) if I want to be able to assign a
contact to an event. In the event table, would I make a reference back to
the contact table? Can I have more than one foreign key reference per table
going to seperate tables? Finally, can I make the reference constraint be
able to be NULL. Meaning, can I make it so that an event can, but doesn't
have to have a contact assigned to it?

The tables (a simplified view) would look like this...

Organization Table:
org_id
org_name

Contact Table:
contact_id
contact_name

Event Table:
event_id
event_name
reference back to org_id in org table
reference back to contact_id in contact_table but there doesn't have to be a
contact associated with this event.

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message greg 2003-12-03 02:57:10 Re: Updating session id based on accesstimeout
Previous Message Iain 2003-12-03 02:18:04 Re: Validity check in to_date?