A script-enabled browser is required for this page to function properly.

ISSUE_SAVEPOINT Built-in

Description

When called from an On-Savepoint trigger, ISSUE_SAVEPOINT initiates the default processing for issuing a savepoint. You can use GET_APPLICATION_PROPERTY (SAVEPOINT_NAME) to determine the name of the savepoint that Oracle Forms would be issuing by default, if no On-Savepoint trigger were present.

This Built-in is included primarily for applications that will run against a non-ORACLE datasource.

Syntax

PROCEDURE ISSUE_SAVEPOINT
(savepoint_name VARCHAR2);

Built-in Type unrestricted procedure

Enter Query Mode no

Parameters

savepoint _name 
 
Name of the savepoint you want to be issued

ISSUE_SAVEPOINT Restrictions

Never issue a savepoint with the name FM_<number>, unless the savepoint name was provided by a call to GET_APPLICATION_PROPERTY. Doing so may cause a conflict with savepoints issued by Oracle Forms.

ISSUE_SAVEPOINT Examples

/*

** Built-in: ISSUE_SAVEPOINT
** Example: Perform Oracle Forms standard savepoint processing.
** Decide whether to use this Built-in based on a
** global flag setup at startup by the form,
** perhaps based on a parameter.
** Trigger: On-Savepoint
*/
DECLARE
sp_name VARCHAR2(80);
BEGIN
/* Get the name of the savepoint Oracle Forms needs to issue
*/
sp_name := Get_Application_Property(SAVEPOINT_NAME);
/* Check the global flag we setup at form startup
*/
IF :Global.Using_Transactional_Triggers = 'TRUE' THEN
User_Exit('my_savept name='||sp_name);
/* Otherwise, do the right thing.
*/
ELSE
Issue_Savepoint(sp_name);
END IF;
END;