enforcing uniqueness across tables
Hi,
I would appreciate advice/best practice on the following aspect of schema design;
I have "equipment" that can be located either "in stock", "in repair" or at a "customer site".
Individually, I think that these are one to many relationships;
stock has many equipments
repair has many equipments
customer site has many equipments.
I think I need separate tables for stock, repair and customer site as the customer site especially has many properties that are only relevant there (but not for stock or repair).
However, equipment can only be in one place at one time. As I'm new to database design, I'm struggling to visualise how to model all this with proper constraints so that equipment doesn't end up in, say, both stock and customer site and would appreciate any pointers that will help me to consolidate what understanding I've managed to learn so far on my own.
Many thanks - Paul
Subject
Written By
Posted
enforcing uniqueness across tables
July 12, 2015 01:31PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.