Oracle® OLAP DML Reference 10g Release 1 (10.1) Part Number B10339-02 |
|
|
View PDF |
A program that you write and that Oracle OLAP checks for by name when an AW ATTACH read/write statement executes. Depending on the value returned by the program, Oracle OLAP executes the code within the program after attaching the analytic workspace.
Note: Oracle OLAP checks for other programs when a user attaches a workspace. See "Startup Programs" for more information. |
Returns
BOOLEAN
TRUE
when Oracle OLAP has successfully set up and attached the analytic workspace; or FALSE
when it has not or when the permit_write
program has thrown an exception
Note: You are encouraged to use the normal return values rather than relying on exceptions to create a return value ofFALSE . |
Syntax
To define a program with the name PERMIT_WRITE
use the syntax shown in DEFINE PROGRAM. Code the actual program as a user-defined function with the following argument.
PERMIT_WRITE (password)
Arguments
See AW ATTACH for an explanation of password.
Note: When a user specifies a password when attaching the analytic workspace, then the password is passed as an argument to the program for processing. |
Notes
A program with the name of permit_write
does not exist within an analytic workspace unless you define and write one. You write a permit_write
as a user-defined functions that returns a BOOLEAN value. You can use the return value to indicate to Oracle OLAP whether or not the user has the right to attach the workspace.
Depending on the statements in the permit_write
program, the user is granted or denied access to specific objects or sets of object values. Within permit_write
program, you can specify PERMIT commands that grant or restrict access to individual workspace objects.
Note: All of the objects referred to in a givenpermit_write must exist in the same analytic workspace. |
Examples
For examples of how attachment programs, see Example 8-14, "Startup Programs".