China
Africa
Explore chapters and articles related to this topic
Microsoft Access 2.0
Published in Paul W. Ross, The Handbook of Software for Engineers and Scientists, 2018
Another concept associated with related databases is referential integrity. The idea behind referential integrity is to preserve the relationship between records in related tables of a database. For instance, in the marketing database example there is a table of companies and a table of contacts at those companies. If a company is deleted and the contacts associated with that company are not deleted then those contacts will remain in the database and not appear in any more queries that include company names. By enforcing referential integrity, Access will automatically report and prevent attempts to delete records that will violate such relationships.
Hybrid state transactional database for product lifecycle management features in a multi-engineer synchronous heterogeneous CAD environment
Published in Computer-Aided Design and Applications, 2018
Devin Shumway, Jonathan Sadler, John L. Salmon
Referential integrity is the process of enforcing every database table to have all foreign keys point to a valid reference [9, 15]. Most database engines will automatically handle references; however, this is only effective when the database has been set up in a way to handle every possible rule. Enforcement of foreign key references in the new NPCF database is vital for keeping the database stable. Referential integrity will help the database recognize corrupted or incomplete data which in turn will be rejected from the database. Rejected data will remain on the client that attempted to send it instead of propagating through each client that is currently in the multi-user session. Referential integrity will also protect the database from corrupt data existing in the part history thus allowing it to be more accurate in storing information. Further checks are implemented on the client side in each CAD system’s plug-in to check that data sent to the database is consistent with the feature the user is trying to create.