Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
This section presents some examples of procedures and functions with external calls.
You must have DBA authority to create procedures or functions that reference external libraries. This requirement is more strict than the RESOURCE authority required for creating other procedures or functions.
You can create a SQL stored procedure that calls a C/C++ function in a library (a Dynamic Link Library (DLL) or shared object) as follows:
CREATE PROCEDURE coverProc( parameter-list ) EXTERNAL NAME 'myFunction@myLibrary' LANGUAGE C_ESQL32;
When you define a stored procedure or function in this way, you are creating a bridge to the function in the external DLL. The stored procedure or function cannot perform any other tasks.
Similarly, you can create a SQL stored function that calls a C/C++ function in a library as follows:
CREATE FUNCTION coverFunc( parameter-list ) RETURNS data-type EXTERNAL NAME 'myFunction@myLibrary' LANGUAGE C_ESQL32;
In these statements, the EXTERNAL NAME clause indicates the function name and library in which it resides. In the example,
myFunction is the exported name of a function in the library, and
myLibrary is the name of the library (for example, myLibrary.dll or myLibrary.so).
The LANGUAGE clause indicates that the function is to be called in an external environment. The LANGUAGE clause can specify one of C_ESQL32, C_ESQL64, C_ODBC32, or C_ODBC64. The 32 or 64 suffix indicates that the function is compiled as a 32-bit or 64-bit application. The ODBC designation indicates that the application uses the ODBC API. The ESQL designation indicates that the application could use the Embedded SQL API, the SQL Anywhere C API, any other non-ODBC API, or no API at all.
If the LANGUAGE clause is omitted, then the library containing the function is loaded into the address space of the database server. When called, the external function will execute as part of the server. In this case, if the function causes a fault, then the database server will be terminated. Because of this, loading and executing functions in an external environment is recommended. If a function causes a fault in an external environment, the database server will continue to run.
The arguments in parameter-list must correspond in type and order to the arguments expected by the library function. The library function accesses the procedure arguments using an API described in External function prototypes.
Any value or result set returned by the external function can be returned by the stored procedure or function to the calling environment.
A stored procedure or function that references an external function can include no other statements: its sole purpose is to take arguments for a function, call the function, and return any value and returned arguments from the function to the calling environment. You can use IN, INOUT, or OUT parameters in the procedure call in the same way as for other procedures: the input values get passed to the external function, and any parameters modified by the function are returned to the calling environment in OUT or INOUT parameters or as the RETURNS result of the stored function.
You can specify operating-system dependent calls, so that a procedure calls one function when run on one operating system, and another function (presumably analogous) on another operating system. The syntax for such calls involves prefixing the function name with the operating system name. The operating system identifier must be Unix. An example follows.
CREATE FUNCTION func ( parameter-list ) RETURNS data-type EXTERNAL NAME 'Unix:email@example.com;firstname.lastname@example.org';
If the list of functions does not contain an entry for the operating system on which the server is running, but the list does contain an entry without an operating system specified, the database server calls the function in that entry.
|Envoyer votre avis sur cette page par email.||Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|