Should referential integrity be handled in Uniface or in the DBMS?
The simple answer is that allowing the DBMS to check for referential integrity is more efficient than having Uniface do it. Referential integrity involves what to do with the related occurrences of the many entitis when the parent one is deleted. Uniface supports, by various means, the options to REStrict, CAScade, or NULlify. Restrict mean that the delete of the one would be prevented if there were related occurrences of the many. Cascade means to delete the related occurrences of the many as well as the one. Nullify means to set the Foreign Key in the many to null. The choice of whether to use Uniface or the DBMS for checking referential integrity depends upon the DBMS’s that you intend to support. If you plan to run your application against many different DBMS’s, or if the DBMS that you are using does not support referential integrity checks, then Uniface must check referential integrity. To do this, simply ensure that all related (many) entities are painted on any form where the us
