Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Diff between Integrity Constraints and Database Triggers?

April 26, 2017database diff integrity triggers

0

Posted

Diff between Integrity Constraints and Database Triggers?

1 Answer

0

Posted

A declarative integrity constraint is a statement about the database that is always true. A constraint applies to existing data in the table and any statement that manipulates the table. A trigger does not apply to data loaded before the definition of the trigger, therefore, it does not guarantee all data in a table conforms to the rules established by an associated trigger. A trigger can be used to enforce transitional constraints where as a declarative integrity constraint cannot be used. Q. what are the properties of the database triggers and form level triggers. A> General NAME: Of the Trigger Sub Class Information: Comments comments for the trigger TriggerType PL/SQL (coding) TriggerText Text(PL/SQL coding) Fire-Enter-Query-Mode yes Execution Hierarchy override(overrides the present level’s trigger with previous/higher hierarchy level’s trigger) Display in keyboard Help yes (the available keys display at the run time) ‘Keyboard Help’ Text TESTING (SHIFT+F5 set the user defined key