By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,479 Members | 1,231 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,479 IT Pros & Developers. It's quick & easy.

Schizophrenic design and solution to it

P: n/a
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
Nov 22 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.