Oracle Call Interface Programmer's Guide Release 2 (9.2) Part Number A96584-01 |
|
More OCI Relational Functions, 105 of 106
Determines the callback that is registered for a handle.
sword OCIUserCallbackGet ( dvoid *hndlp, ub4 type, dvoid *ehndlp, ub4 fcode, ub4 when OCIUserCallback (*callbackp) (/*_ dvoid *ctxp, dvoid *hndlp, ub4 type, ub4 fcode, ub1 when, sword returnCode, ub4 *errnop, va_list arglist _*/), dvoid **ctxpp OCIUcb *ucbDesc );
This is the handle whose type is specified by the type parameter.
The handle type. The valid handle type is:
fcode
made on the environment handle.The OCI error or environment handle. If there is an error, it is recorded in ehndlp
and this function returns OCI_ERROR. Diagnostic information can be obtained by calling OCIErrorGet()
.
A unique function code of an OCI function. These are listed in Table 16-8, "OCI Function Codes".
Defines when the callback is invoked. Valid modes are:
OCIUserCallbackRegister()
.A pointer to a callback function pointer. This returns the function that is currently registered for these values of fcode
, when
, and hndlp
. The value returned would be NULL if no callback is registered for this case.
See Also:
For information about the parameters of |
A pointer to return context for the currently registered callback.
An OCI provided descriptor. This descriptor is passed by OCI in the environment callback. It contains the priority at which the callback would be registered at. If the ucbDesc
parameter is specified as NULL
, then this callback has the highest priority.
User callbacks registered statically (as opposed to those registered dynamically in a package) use a null descriptor because they do not have a ucb descriptor to use.
This function finds out what callback is registered for a particular handle.
See Also:
For information on the restrictions of the use of callback functions, see "Restrictions on Callback Functions". |
|
Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|