Abstract
The entity-relationship (ER) model is clearly established as a conceptual model of choice when building relational database systems. Once the ER model is built, it can be mapped algorithmically to the relational model and consequently to the data definition language (DDL) of SQL. Algorithmic mapping of the ER model to the relational model can produce foreign keys referencing each other’s tables cyclically. This cyclical reference of foreign keys generates irresolvable deadlocks when enforcing the referential integrity rule using the cascading option. However, it is not obvious for database designers while building an ER model. In this article, we provide a set of rules of ER modeling for avoiding cyclical references of foreign keys.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
