sql relay的c++接口

原创 2005年06月02日 10:34:00
Programming with SQL Relay using the C++ API

Compiling an SQL Relay Client Program

When writing an SQL Relay client program using the C++ API, you need to include the sqlrclient.h file.

You'll also need to link against the sqlrclient and rudiments libraries. The include file is usually found in /usr/local/firstworks/include and the libraries are usually found in /usr/local/firstworks/lib.

The command to compile your .C file to object code will look something like this (assuming you're using GNU C++):

g++ -I/usr/local/firstworks/include -c myprogram.C

The command to compile your .o file to an executable will look something like this (assuming you're using GNU C++):

g++ -o myprogram myprogram.o -L/usr/local/firstworks/lib -lsqlrclient -lrudiments
Establishing a Session

To use SQL Relay, you have to identify the connection that you intend to use.


main() {

       sqlrconnection      con= sqlrconnection(,,,,,,);

       ... execute some queries ...

        con;
}

After calling the constructor, a session is established when the first query, ping() or identify() is run.

For the duration of the session, the client stays connected to a database connection daemon. While one client is connected, no other client can connect. Care should be taken to minimize the length of a session.

If you're using a transactional database, ending a session has a catch. Database connection daemons can be configured to send either a commit or rollback at the end of a session if DML queries were executed during the session with no commit or rollback. Program accordingly.

Executing Queries

Allocate a cursor, then call sendQuery() or sendFileQuery() to run a query. The same cursor may be used over and over.


main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->sendQuery();

        ... do some stuff that takes a short time ...

        cur->sendFileQuery(,);
        con->endSession();

        ... do some stuff that takes a long time ...

        cur->sendQuery();
        con->endSession();

        ... process the result set ...

         cur;
         con;
}

Note the call to endSession() after the call to sendFileQuery(). Since the program does some stuff that takes a long time between that query and the next, ending the session there allows another client an opportunity to use that database connection while your client is busy. The next call to sendQuery() establishes another session. Since the program does some stuff that takes a short time between the first two queries, it's OK to leave the session open between them.

Commits and Rollbacks

If you need to execute a commit or rollback, you should use the commit() and rollback() methods of the sqlrconnection class rather than sending a "commit" or "rollback" query. There are two reasons for this. First, it's much more efficient to call the methods. Second, if you're writing code that can run on transactional or non-transactional databases, some non-transactional databases will throw errors if they receive a "commit" or "rollback" query, but by calling the commit() and rollback() methods you instruct the database connection daemon to call the commit and rollback API methods for that database rather than issuing them as queries. If the API's have no commit or rollback methods, the calls do nothing and the database throws no error. This is especially important when using SQL Relay with ODBC.

You can also turn Autocommit on or off with the autoCommitOn() and autoCommitOff() methods of the sqlrconnection class. When Autocommit is on, the database performs a commit after each successful DML or DDL query. When Autocommit is off, the database commits when the client instructs it to, or (by default) when a client disconnects. For databases that don't support Autocommit, autoCommitOn() and autoCommitOff() have no effect.

Temporary Tables

Some databases support temporary tables. That is, tables which are automatically dropped or truncated when an application closes it's connection to the database or when a transaction is committed or rolled back.

For databases which drop or truncate tables when a transaction is committed or rolled back, temporary tables work naturally.

However, for databases which drop or truncate tables when an application closes it's connection to the database, there is an issue. Since SQL Relay maintains persistent database connections, when an application disconnects from SQL Relay, the connection between SQL Relay and the database remains, so the database does not know to drop or truncate the table. To remedy this situation, SQL Relay parses each query to see if it created a temporary table, keeps a list of temporary tables and drops (or truncates them) when the application disconnects from SQL Relay. Since each database has slightly different syntax for creating a temporary table, SQL Relay parses each query according to the rules for that database.

In effect, temporary tables should work when an application connects to SQL Relay in the same manner that they would work if the application connected directly to the database.

Catching Errors

If your call to sendQuery() or sendFileQuery() returns a 0, the query failed. You can find out why by calling errorMessage().



main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

         (!cur->sendQuery()) {
                cout << cur->errorMessage() << endl;
        }

         cur;
         con;
}

Substitution and Bind Variables

Programs rarely execute fixed queries. More often than not, some part of the query is dynamically generated. It's convenient to store queries in files so they can be changed by a non-C++ programmer. The SQL Relay API provides methods for making substitutions and binds in those queries.

For a detailed discussion of substitutions and binds, see this document.

Rather than just calling sendFileQuery() you call prepareFileQuery(), substitution(), inputBind() and executeQuery().

/usr/local/myprogram/sql/myquery.sql:

	select * from mytable $(whereclause)
Program code:

main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->prepareFileQuery(,);
        cur->substitution(,);
        cur->inputBind(,);
        cur->executeQuery();

        ... process the result set ...

         cur;
         con;
}

If you're using a database with an embedded procedural language, you may want to retrieve data from a call to one of it's functions. To facilitate this, SQL Relay provides the defineOutputBind() and getOutputBind() methods.

PL/SQL Procedure:
 sp_mytable  types.cursorType
l_cursor types.cursorType;

        OPEN l_cursor   *  mytable;
         l_cursor;
;

Program code:

main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->prepareQuery();
        cur->inputBind(,);
        cur->inputBind(,);
        cur->defineOutputBind(,);
        cur->executeQuery();
             result=atoi(cur->getOutputBind());
        con->endSession();

        ... do something with the result ...

         cur;
         con;
}

The getOutputBind() method returns a NULL value as an empty string. If you would it to come back as a NULL instead, you can call the getNullsAsNulls() method. To revert to the default behavior, you can call getNullsAsEmptyStrings().

The getOutputBind() method returns a string, if you would like to get the value as a long or double, you can use getOutputBindAsLong() or getOutputBindAsDouble().

If you are using Oracle 8i or higher, you can insert data into BLOB and CLOB columns using the inputBindBlob(), inputBindClob() methods.

If you are curious how many bind variables have been declared in a query, you can call countBindVariables() after preparing the query.


main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->executeQuery();

            imagedata[];
            imagelength;

        ... read an image from a file into imagedata and the length of the
                file into imagelength ...

            description[];
            desclength;

        ... read a description from a file into description and the length of
                the file into desclength ...

        cur->prepareQuery();
        cur->inputBindBlob(,imagedata,imagelength);
        cur->inputBindClob(,description,desclength);
        cur->executeQuery();

         cur;
         con;
}

Likewise, with Oracle 8i, you can retreive BLOB or CLOB data using defineOutputBindBlob(), defineOutputBindClob(), getOutputBind() and getOutputBindLength().


main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->prepareQuery();
        cur->defineOutputBindBlob();
        cur->defineOutputBindClob();
        cur->executeQuery();

            *image=cur->getOutputBind();
            imagelength=cur->getOutputBindLength();

            *desc=cur->getOutputBind();
            *desclength=cur->getOutputBindLength();

        con->endSession();

        ... do something with image and desc ...

         cur;
         con;
}

Sometimes it's convenient to bind a bunch of variables that may or may not actually be in the query. For example, if you are building a web based application, it may be easy to just bind all the form variables/values from the previous page, even though some of them don't appear in the query. Databases usually generate errors in this case. Calling validateBinds() just prior to calling executeQuery() causes the API to check the query for each bind variable before actually binding it, preventing those kinds of errors. There is a performance cost associated with calling validateBinds().

Re-Binding and Re-Execution

Another feature of the prepare/bind/execute paradigm is the ability to prepare, bind and execute a query once, then re-bind and re-execute the query over and over without re-preparing it. If your backend database natively supports this paradigm, you can reap a substantial performance improvement.


main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->prepareQuery();
        cur->inputBind(,);
        cur->executeQuery();

        ... process the result set ...

        cur->clearBinds();
        cur->inputBind(,);
        cur->executeQuery();

        ... process the result set ...

        cur->clearBinds();
        cur->inputBind(,);
        cur->executeQuery();

        ... process the result set ...

         cur;
         con;
}
Accessing Fields in the Result Set

The rowCount(), colCount() and getField() methods are useful for processing result sets.



main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->sendQuery();
        con->endSession();

         ( row=; row<cur->rowCount(); row++) {
                 ( col=; col<cur->colCount(); col++) {
                        cout << cur->getField(row,col) << ;
                }
                cout << endl;
        }

         cur;
         con;
}

The getField() method returns a string. If you would like to get a field as a long or double, you can use getFieldAsLong() and getFieldAsDouble().

You can also use getRow() which returns a NULL-terminated array of the fields in the row.



main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->sendQuery();
        con->endSession();

         ( row=; row<cur->rowCount(); row++) {
                    **rowarray=cur->getRow(row);
                 ( col=; col<cur->colCount(); col++) {
                        cout << rowarray[col] << ;
                }
                cout << endl;
        }

         cur;
         con;
}

The getField() and getRow() methods return NULL fields as empty strings. If you would like them to come back as NULL's instead, you can call the getNullsAsNulls() method. To revert to the default behavior, you can call getNullsAsEmptyStrings().

If you want to access the result set, but don't care about the column information (column names, types or sizes) and don't mind getting fields by their numeric index instead of by name, you can call the dontGetColumnInfo() method prior to executing your query. This can result in a performance improvement, especially when many queries with small result sets are executed in rapid succession. You can call getColumnInfo() again later to turn off this feature.

Dealing With Large Result Sets

SQL Relay normally buffers the entire result set. This can speed things up at the cost of memory. With large enough result sets, it makes sense to buffer the result set in chunks instead of all at once.

Use setResultSetBufferSize() to set the number of rows to buffer at a time. Calls to getRow() and getField() cause the chunk containing the requested field to be fetched. Rows in that chunk are accessible but rows before it are not.

For example, if you setResultSetBufferSize(5) and execute a query that returns 20 rows, rows 0-4 are available at once, then rows 5-9, then 10-14, then 15-19. When rows 5-9 are available, getField(0,0) will return NULL and getField(11,0) will cause rows 10-14 to be fetched and return the requested value.

When buffering the result set in chunks, don't end the session until after you're done with the result set.

If you call setResultSetBufferSize() and forget what you set it to, you can always call getResultSetBufferSize().

When buffering a result set in chunks, the rowCount() method returns the number of rows returned so far. The firstRowIndex() method returns the index of the first row of the currently buffered chunk.



main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->setResultSetBufferSize();

        cur->sendQuery();

             done=;
             row=;
            *field;
         (!done) {
                 ( col=; col<cur->colCount(); col++) {
                         (field=cur->getField(row,col)) {
                                cout << field << ;
                        }  {
                                done=;
                        }
                }
                cout << endl;
                row++;
        }

        cur->sendQuery();

        ... process this query's result set in chunks also ...

        cur->setResultSetBufferSize();

        cur->sendQuery();

        ... process this query's result set all at once ...

        con->endSession();

         cur;
         con;
}
Cursors

Cursors make it possible to execute queries while processing the result set of another query. You can select rows from a table in one query, then iterate through it's result set, inserting rows into another table, using only 1 database connection for both operations.

For example:


main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cursor1= sqlrcursor(con);
        sqlrcursor          *cursor2= sqlrcursor(con);

        cursor1->setResultSetBufferSize();
        cursor1->sendQuery();

             index=;
         (!cursor1->endOfResultSet()) {
                cursor2->prepareQuery();
                cursor2->inputBind(,cursor1->getField(index,));
                cursor2->inputBind(,cursor1->getField(index,));
                cursor2->inputBind(,cursor1->getField(index,));
                cursor2->executeQuery();
        }

         cursor2;
         cursor1;
         con;
}

Prior to SQL Relay version 0.25, you would have had to buffer the first result set or use 2 database connections instead of just 1.

If you are using stored procedures with Oracle 8i or higher, a stored procedure can execute a query and return a cursor. A cursor bind variable can then retrieve that cursor. Your program can retrieve the result set from the cursor. All of this can be accomplished using defineOutputBindCursor(), getOutputBindCursor() and fetchFromOutputBindCursor().

PL/SQL Procedure:
 sp_mytable  types.cursorType
l_cursor types.cursorType;

        OPEN l_cursor   *  mytable;
         l_cursor;
;

Program code:


main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->prepareQuery();
        cur->defineOutputBindCursor();
        cur->executeQuery();

        sqlrcursor      *bindcur=cur->getOutputBindCursor();
        bindcur->fetchFromBindCursor();

        
         ( i=; i<bindcur->rowCount(); i++) {
                 ( j=; j<bindcur->colCount(); j++) {
                        cout << bindcur->getField(i,j) << ;
                }
                cout << endl;
        }

         bindcur;

         cur;
         con;
}

The number of cursors simultaneously available per-connection is set at compile time and defaults to 5.

Getting Column Information

For each column, the API supports getting the name, type and length of each field. All databases support these attributes. The API also supports getting the precision, scale, length of the longest field, and whether the column is nullable, the primary key, unique, part of a key, unsigned, zero-filled, binary, or an auto-incrementing field. However, not all databases support these attributes. If a database doesn't support an attribute, it is always returned as false.



main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->sendQuery();
        con->endSession();

         ( i=; i<cur->colCount(); i++) {
                cout <<  << cur->getColumnName(i) << endl;
                cout <<  << cur->getColumnType(i) << endl;
                cout <<  << cur->getColumnLength(i) << endl;
                cout <<  << cur->getColumnPrecision(i) << endl;
                cout <<  << cur->getColumnScale(i) << endl;
                cout <<  << cur->getLongest(i) << endl;
                cout <<  << cur->getColumnIsNullable(i) << endl;
                cout <<  << cur->getColumnIsPrimaryKey(i) << endl;
                cout <<  << cur->getColumnIsUnique(i) << endl;
                cout <<  << cur->getColumnIsPartOfKey(i) << endl;
                cout <<  << cur->getColumnIsUnsigned(i) << endl;
                cout <<  << cur->getColumnIsZeroFilled(i) << endl;
                cout <<  << cur->getColumnIsBinary(i) << endl;
                cout <<  << cur->getColumnIsAutoIncrement(i) << endl;
                cout << endl;
        }

         cur;
         con;
}

Some databases force column names to upper case, others force column names to lower case, and others still support mixed-case column names. Sometimes, when migrating between databases, you can run into trouble. You can use upperCaseColumnNames() and lowerCaseColumnNames() to cause column names to be converted to upper or lower case, or you can use mixedCaseColumnNames() to cause column names to be returned in the same case as they are defined in the database.



main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        
        cur->upperCaseColumnNames();
        cur->sendQuery();
        con->endSession();

         ( i=; i<cur->colCount(); i++) {
                cout <<  << cur->getColumnName(i) << endl;
                cout << endl;
        }

        
        cur->lowerCaseColumnNames();
        cur->sendQuery();
        con->endSession();

         ( i=; i<cur->colCount(); i++) {
                cout <<  << cur->getColumnName(i) << endl;
                cout << endl;
        }

        
        cur->mixedCaseColumnNames();
        cur->sendQuery();
        con->endSession();

         ( i=; i<cur->colCount(); i++) {
                cout <<  << cur->getColumnName(i) << endl;
                cout << endl;
        }

         cur;
         con;
}
Stored Procedures

Many databases support stored procedures. Stored procedures are sets of queries and procedural code that are executed inside of the database itself. For example, a stored procedure may select rows from one table, iterate through the result set and, based on the values in each row, insert, update or delete rows in other tables. A client program could do this as well, but a stored procedure is generally more efficient because queries and result sets don't have to be sent back and forth between the client and database. Also, stored procedures are generally stored in the database in a compiled state, while queries may have to be re-parsed and re-compiled each time they are sent.

While many databases support stored procedures. The syntax for creating and executing stored procedures varies greatly between databases.

SQL Relay supports stored procedures for most databases, but there are some caveats. Stored procedures are not currently supported when using FreeTDS against Sybase or Microsoft SQL Server. Blob/Clob bind variables are only supported in Oracle 8i or higher. Sybase stored procedures must use varchar output parameters.

Stored procedures typically take input paramters from client programs through input bind variables and return values back to client programs either through bind variables or result sets. Stored procedures can be broken down into several categories, based on the values that they return. Some stored procedures don't return any values, some return a single value, some return multiple values and some return entire result sets.

No Values

Some stored procedures don't return any values. Below are examples, illustrating how to create, execute and drop this kind of stored procedure for each database that SQL Relay supports.

Oracle

To create the stored procedure, run a query like the following.

  testproc(in1  , in2  , in3  ) 

          mytable  (in1,in2,in3);
;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->executeQuery();

To drop the stored procedure, run a query like the following.

  testproc
Sybase and Microsoft SQL Server

To create the stored procedure, run a query like the following.

  testproc @in1 int, @in2 , @in3 () 
          mytable  (@in1,@in2,@in3)

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->executeQuery();

To drop the stored procedure, run a query like the following.

  testproc
Interbase and Firebird

To create the stored procedure, run a query like the following.

  testproc(in1 , in2 , in3 ()) 

          mytable  (in1,in2,in3);
        suspend;
;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->executeQuery();

To drop the stored procedure, run a query like the following.

  testproc
DB2

To create the stored procedure, run a query like the following.

  testproc( in1 int,  in2 double,  in3 ()) language sql

          mytable  (in1,in2,in3);
;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->executeQuery();

To drop the stored procedure, run a query like the following.

  testproc
Postgresql

To create the stored procedure, run a query like the following.

  testproc(int,,()) returns void  '

          mytable  ($,$,$);
        ;
;' language plpgsql

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->executeQuery();

To drop the stored procedure, run a query like the following.

  testproc

Single Values

Some stored procedures return single values. Below are examples, illustrating how to create, execute and drop this kind of stored procedure for each database that SQL Relay supports.

Oracle

In Oracle, stored procedures can return values through output parameters or as return values of the procedure itself.

Here is an example where the procedure itself returns a value. Note that Oracle calls these functions.

To create the stored procedure, run a query like the following.

  testproc(in1  , in2  , in3  ) returns  

         in1;
;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->executeQuery();
    *result=cur->getField(,);

To drop the stored procedure, run a query like the following.

  testproc

Here is an example where the value is returned through an output parameter.

To create the stored procedure, run a query like the following.

  testproc(in1  , in2  , in3  , out1  ) 

        out1:=in1;
;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->defineOutputBind(,);
cur->executeQuery();
    *result=cur->getOutputBind();

To drop the stored procedure, run a query like the following.

  testproc
Sybase and Microsoft SQL Server

In Sybase and Microsoft SQL Server, stored procedures return values through output parameters rather than as return values of the procedure itself.

To create the stored procedure, run a query like the following.

  testproc @in1 int, @in2 , @in3 (), @out1 int output 
         @out1=convert((),@in1)

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->defineOutputBind(,);
cur->executeQuery();
    *result=cur->getOutputBind();

To drop the stored procedure, run a query like the following.

  testproc
Interbase and Firebird

To create the stored procedure, run a query like the following.

  testproc(in1 , in2 , in3 ()) returns (out1 ) 

        out1=in1;
        suspend;
;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->executeQuery();
    *result=cur->getField(,);

Alternatively, you can run a query like the following and receive the result using an output bind variable. Note that in Interbase/Firebird, input and output bind variable indices are distict from one another. The index of the output bind variable is 1 rather than 4, even though there were 3 input bind variables.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->defineOutputBind(,);
cur->executeQuery();
    *result=cur->getOutputBind();

To drop the stored procedure, run a query like the following.

  testproc
DB2

In DB2, stored procedures return values through output parameters rather than as return values of the procedure itself.

To create the stored procedure, run a query like the following.

  testproc( in1 int,  in2 double,  in3 (),  out1 int) language sql

         out1 = in1;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->defineOutputBind(,);
cur->executeQuery();
    *result=cur->getOutputBind();

To drop the stored procedure, run a query like the following.

  testproc
Postgresql

To create the stored procedure, run a query like the following.

  testfunc(int,,()) returns int  '
declare
        in1 int;
        in2 ;
        in3 ();

        in1:=$;
        ;
;
' language plpgsql

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->executeQuery();
    *result=cur->getField(,);

To drop the stored procedure, run a query like the following.

  testfunc(int,,())

Multiple Values

Some stored procedures return multiple values. Below are examples, illustrating how to create, execute and drop this kind of stored procedure for each database that SQL Relay supports.

Oracle

In Oracle, stored procedures can return values through output parameters or as return values of the procedure itself. If a procedure needs to return multiple values, it can return one of them as the return value of the procedure itself, but the rest must be returned through output parameters.

To create the stored procedure, run a query like the following.

  testproc(in1  , in2  , in3  , out1  , out2  , out3  ) 

        out1:=in1;
        out2:=in2;
        out3:=in3;
;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->defineOutputBind(,);
cur->defineOutputBind(,);
cur->defineOutputBind(,);
cur->executeQuery();
    *out1=cur->getOutputBind();
    *out2=cur->getOutputBind();
    *out3=cur->getOutputBind();

To drop the stored procedure, run a query like the following.

  testproc
Sybase and Microsoft SQL Server

To create the stored procedure, run a query like the following.

  testproc @in1 int, @in2 , @in3 (), @out1 int output, @out2 int output, @out3 int output 
         @out1=convert((),@in1),
                @out2=convert((),@in2),
                @out2=convert((),@in2)

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->defineOutputBind(,);
cur->defineOutputBind(,);
cur->defineOutputBind(,);
cur->executeQuery();
    *out1=cur->getOutputBind();
    *out2=cur->getOutputBind();
    *out3=cur->getOutputBind();

To drop the stored procedure, run a query like the following.

  testproc
Interbase and Firebird

To create the stored procedure, run a query like the following.

  testproc(in1 , in2 , in3 ()) returns (out1 , out2 , out3 ()) 

        out1=in1;
        out2=in2;
        out3=in3;
        suspend;
;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->executeQuery();
    *out1=cur->getField(,);
    *out2=cur->getField(,);
    *out3=cur->getField(,);

Alternatively, you can run a query like the following and receive the result using a output bind variables. Note that in Interbase/Firebird, input and output bind variable indices are distict from one another. The index of the first output bind variable is 1 rather than 4, even though there were 3 input bind variables.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->defineOutputBind(,);
cur->defineOutputBind(,);
cur->defineOutputBind(,);
cur->executeQuery();
    *out1=cur->getOutputBind();
    *out2=cur->getOutputBind();
    *out3=cur->getOutputBind();

To drop the stored procedure, run a query like the following.

  testproc
DB2

To create the stored procedure, run a query like the following.

  testproc( in1 int,  in2 double,  in3 (),  out1 int,  out2 double,  out3 ()) language sql

         out1 = in1;
         out2 = in2;
         out3 = in3;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->defineOutputBind(,);
cur->defineOutputBind(,);
cur->defineOutputBind(,);
cur->executeQuery();
    *out1=cur->getOutputBind();
    *out2=cur->getOutputBind();
    *out3=cur->getOutputBind();

To drop the stored procedure, run a query like the following.

  testproc
Postgresql

To create the stored procedure, run a query like the following.

  testfunc(int,,()) returns record  '
declare
        output record;

         $,$,$  output;
         output;
;
' language plpgsql

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->inputBind(,);
cur->inputBind(,,,);
cur->inputBind(,);
cur->executeQuery();
    *out1=cur->getField(,);
    *out2=cur->getField(,);
    *out3=cur->getField(,);

To drop the stored procedure, run a query like the following.

  testfunc(int,,())

Result Sets

Some stored procedures return entire result sets. Below are examples, illustrating how to create, execute and drop this kind of stored procedure for each database that SQL Relay supports.

Oracle

To create the stored procedure, run a query like the following.

  replace package types 
         cursorType  ref ;
;

  testproc  types.cursortype 
        l_cursor    types.cursorType;

        open l_cursor   *  mytable;
         l_cursor;
;

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->prepareQuery();
cur->defineOutputBindCursor();
cur->executeQuery();
sqlrcursor      *bindcur=cur->getOutputBindCursor();
bindcur->fetchFromBindCursor();
    *field00=bindcur->getField(,);
    *field01=bindcur->getField(,);
    *field02=bindcur->getField(,);
    *field10=bindcur->getField(,);
    *field11=bindcur->getField(,);
    *field12=bindcur->getField(,);
...

To drop the stored procedure, run a query like the following.

  testproc
 package types
Sybase and Microsoft SQL Server

Stored procedures in Sybase and Microsoft SQL Server can return a result set if the last command in the procedure is a select query, however SQL Relay doesn't currently support stored procedures that return result sets.

Interbase and Firebird

Stored procedures in Interbase and Firebird can return a result set if a select query in the procedure selects values into the output parameters and then issues a suspend command, however SQL Relay doesn't currently support stored procedures that return result sets.

DB2

Stored procedures in DB2 can return a result set if the procedure is declared to return one, however SQL Relay doesn't currently support stored procedures that return result sets.

Postgresql

To create the stored procedure, run a query like the following.

  testfunc() returns setof record  '
        declare output record;

         output   *  mytable 
                 next output;
         ;
        ;
;
' language plpgsql

To execute the stored procedure from an SQL Relay program, use code like the following.

cur->sendQuery();
    *field00=cur->getField(,);
    *field01=cur->getField(,);
    *field02=cur->getField(,);
    *field10=cur->getField(,);
    *field11=cur->getField(,);
    *field12=cur->getField(,);
...

To drop the stored procedure, run a query like the following.

  testfunc
Caching The Result Set

Say you're writing a web-based report where a query with a huge result set is executed and 20 rows are displayed per page. Rather than rerunning the query for every page every time and dumping all but the 20 rows you want to display, you can run the query once, cache the result set to a local file and just open the file for each page of the report.

First CGI:


main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

	... generate a unique filename ...

        cur->cacheToFile(filename);
        cur->setCacheTtl();
        cur->sendQuery();
        con->endSession();
        cur->cacheOff();

        ... pass the filename to the next page ...

         cur;
         con;
}

Second CGI:



main() {

        ... get the filename from the previous page ...

        ... get the page to display from the previous page ...

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->openCachedResultSet(filename);
        con->endSession();

         ( row=pagetodisplay*; row<(pagetodisplay+)*; row++) {
                 ( col=; col<cur->colCount(); col++) {
                        cout << cur->getField(row,col) << ;
                }
                cout << endl;
        }

         cur;
         con;
}
Suspending and Resuming Sessions

Sometimes web-based applications need a single database transaction to span multiple pages. Since SQL Relay sessions can be suspended and resumed, this is possible.

First CGI:


main() {

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        cur->sendQuery();
             port=cur->getConnectionPort();
            *socket=cur->getConnectionSocket();
             rs=cur->getResultSetId();
        cur->suspendResultSet();
        con->suspendSession();

        ... pass the rs, port and socket to the next page ...

         cur;
         con;
}

Second CGI:


main() {

        ... get rs, port and socket from previous page ...

        sqlrconnection      *con= sqlrconnection(,,,,,,);
        sqlrcursor          *cur= sqlrcursor(con);

        con->resumeSession(port,socket);
        cur->resumeResultSet(rs);
        cur->sendQuery();
        con->endSession();

         cur;
         con;
}

You can also distribute the processing of a result set across a series of CGI's using suspended sessions. If you're buffering a result set in chunks instead of all at once and suspend a session, when you resume the session you can continue to retrieve rows from the result set.

Similarly, if you're buffering a result set in chunks, caching that result set and suspend your session. When you resume the session, you can continue caching the result set. You must use resumeCachedResultSet() instead of resumeResultSet() however.

SQL Relay使用详解

http://www.ydmsh.com/www/Blog/Show/id/152/ episode01 What Is     此文算是我对这段时间学习SQL Relay的汇总和总结...

SQL-Relay学习笔记(3)

安全性保障Kerberos 和活动目录(Active Directory)加密认证SQL Relay支持Kerberos加密和认证。 当启用Kerberos和Active Directory加密认证...

SQL-Relay参数文档

  • 2016年09月28日 23:11
  • 91KB
  • 下载

SQL-Relay学习笔记(1)

SQL-Relay笔记基本配置文件位置Unix和Linux下其配置文件位于 Built from source - /usr/local/firstworks/etc/sqlrelay.conf R...

SQL Relay使用

一、SQL Relay是什么? SQL Relay是一个开源的数据库池连接代理服务器 二、SQL Relay支持哪些数据库? * Oracle * MySQL * m...

Error reading relay log event: slave SQL thread was killed

1.版本 1)操作系统  cat /etc/issue Red Hat Enterprise Linux Server release 5.5 (Tikanga) Kernel \r on an ...

PHP数据库连接池SQL Relay安装使用

SQL Relay按照其官网http://sqlrelay.sourceforge.net/index.html上所说是:A powerful database connection manageme...

excel与sql数据接口

  • 2012年11月10日 21:50
  • 298KB
  • 下载

Relay: 全新的React数据获取框架

React在前端领域开启了一个新的时代。随着Facebook发布并开源React,它迅速成为大量技术公司 运用在生产环境中的一款流行的库。在本文中,我们将会讨论的是一个全新的React附属框架——Re...
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:sql relay的c++接口
举报原因:
原因补充:

(最多只允许输入30个字)