11.01.2013 Views

Oracle Forms Developer – Form Builder Reference, Volume 1

Oracle Forms Developer – Form Builder Reference, Volume 1

Oracle Forms Developer – Form Builder Reference, Volume 1

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

On-Check-Unique trigger<br />

Description<br />

During a commit operation, the On-Check-Unique trigger fires when <strong>Form</strong> <strong>Builder</strong> normally checks that<br />

primary key values are unique before inserting or updating a record in a base table. It fires once for each<br />

record that has been inserted or updated.<br />

Replaces the default processing for checking record uniqueness. When a block has the PRIMKEYB<br />

property set to Yes, <strong>Form</strong> <strong>Builder</strong>, by default, checks the uniqueness of a record by constructing and<br />

executing the appropriate SQL statement to select for rows that match the current record’s primary key<br />

values. If a duplicate row is found, <strong>Form</strong> <strong>Builder</strong> displays message FRM-40600: Record has already<br />

been inserted.<br />

For a record that has been marked for insert, <strong>Form</strong> <strong>Builder</strong> always checks for unique primary key values.<br />

In the case of an update, <strong>Form</strong> <strong>Builder</strong> checks for unique primary key values only if one or more items<br />

that have the Primary Key item property have been modified.<br />

Definition Level<br />

form, block<br />

Legal Commands<br />

SELECT statements, PL/SQL, unrestricted built-ins<br />

Enter Query Mode no<br />

Usage Notes<br />

To perform the default processing from this trigger, call the CHECK_RECORD_UNIQUENESS builtin.<br />

On Failure<br />

no effect<br />

Fires In<br />

Check Record Uniqueness<br />

Post and Commit Transactions<br />

See Process Flowcharts<br />

434

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!