| From: | "nobody" <nobody(at)nowhere(dot)near(dot)here> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Schizophrenic design and solution to it |
| Date: | 2004-02-12 20:01:39 |
| Message-ID: | c0gm32$1mmo$1@news.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I have a database which design I inherited. It is not PostgreSQL but I hope
somebody here could help.
There are two tables "RemovalProject" and "Carriage. Both are 90 percent
equal and basicaly represent a transport job.
I need to extend the database to handle allocation of labour to both
RemovalProject and Carriage. But because they are two separate tables, it
looks I will have to develop two systems for labour allocation - I simply
cannot concieve one table linked to both, RemovalProject and Carriage, to
represent the labour allocation and have the SQL to handle "conditional"
join.
How would you resolve this design issue?
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashish Mahabal | 2004-02-12 20:19:16 | postgresql system column errors |
| Previous Message | Richard Welty | 2004-02-12 19:54:47 | Re: I want to use postresql for this app, but... |