Re: enforcing uniqueness across tables
> thought that it was best practice to enforce business logic in the database itself
Yes, and the interesting cases are when priorities conflict, so the interesting question is, what priorities entail that location be stored in repair and customer tables, why not instead keep a location Set column in stock, and use repair & customer tables just to store repair & rental details respectively?
Subject
Written By
Posted
Re: enforcing uniqueness across tables
July 13, 2015 11:56AM
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.