Referential IntegrityIn any relational database there is the need to ensure that the data conforms to business rules. kinodb automatically maintains referential integrity and polices the relationship cardinalities. For instance, in a contacts database it might be valid for a person to exist without an associated company, whilst in an order processing system it might be required that each person record is associated with a particular company kinodb also ensures that lifecycle rules are not violated. For instance, if each person must belong to a company, kinodb allows you to specify either that companies cannot be deleted if they have associated people, or that the people records will be deleted if their associated company record is deleted. The image below shows how a referential constraint for a list relationship is applied. 
kinodb's management of referential integrity, and the use of virtual fields combine to encourage the implementation of fully normalised data models regardless of complexity. The benefits of this are reduced development timescales and the production of more maintainable systems. |
See AlsoOther topics in this section: Back to Technical Overview |
 | Home | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Products | |||||||||
| ||||||||||
| Services | |||||||||
|
Downloads and screenshots | |||||||||
|
Case studies | |||||||||
| FAQs | |||||||||
| About datb | |||||||||
| Contact us |
