OTL 4.0, Example 564 (otl_stream::clean(), cancelling Result Set's fetch sequence, Sybase SQL Server)

This example demonstrates the extended functionality of the otl_stream::clean() function.

Source Code

#include <iostream>
using namespace std;

#include <stdio.h>
#define OTL_ODBC_UNIX // Compile OTL 4.0/ODBC
#include <otlv4.h> // include the OTL 4.0 header file

otl_connect db; // connect object

void insert()
// insert rows into table

 otl_stream o(50, // buffer size
              "insert into test_tab values(:f1<float>,:f2<char[31]>)", 
                 // SQL statement
              db // connect object
             );
 char tmp[32];

 for(int i=1;i<=100;++i){
  sprintf(tmp,"Name%d",i);
  o<<(float)i<<tmp;
 }
}

void select()

 otl_stream i(50, // buffer size
              "{call my_proc(:f1<int,in>)}",
                 // implicit SELECT statement
              db, // connect object
              otl_implicit_select // implicit SELECT statement
             ); 
 
 float f1;
 char f2[31];

 i<<8; // assigning :f1 = 8
   // SELECT automatically executes when all input variables are
   // assigned. First portion of output rows is fetched to the buffer

 int n=0;
 cout<<"====> Starting a fetch sequence...."<<endl;
 while(!i.eof()){ // while not end-of-data
  ++n;
  i>>f1>>f2;
  cout<<"f1="<<f1<<", f2="<<f2<<endl;
  if(n>=3){
   // breaking the fetch sequence after 3 rows are fetched, and 
   // "cleaning" the state of the SELECT stream.
   cout<<"Cancelling the fetch sequence after 3 rows are fetched"<<endl;
   i.clean();
   break;
  }
 }

 cout<<"====> Starting another fetch sequence..."<<endl;
 i<<4; // assigning :f1 = 4
   // SELECT automatically executes when all input variables are
   // assigned. First portion of output rows is fetched to the buffer

 while(!i.eof()){ // while not end-of-data
  i>>f1>>f2;
  cout<<"f1="<<f1<<", f2="<<f2<<endl;
 }

}

int main()
{
 otl_connect::otl_initialize(); // initialize ODBC environment
 try{

  db.rlogon("scott/tigger@freetds_sybsql"); // connect to MS SQL Server
// It's recommended to use auto_commit_off() when OTL is used
// with FreeTDS/ODBC against Sybase in order to set the DB
// session's auto-commit to OFF. otl_connect::rlogon()'s auto-commit
// parameter has not effect. auto_commit_off() is a workaround, until
// a fix becomes available.
db.auto_commit_off();

  otl_cursor::direct_exec
   (
    db,
    "drop table test_tab",
    otl_exception::disabled // disable OTL exceptions
   ); // drop table

  otl_cursor::direct_exec
   (
    db,
    "create table test_tab(f1 int, f2 varchar(30))"
    );  // create table

  otl_cursor::direct_exec
   (
    db,
    "drop procedure my_proc",
    otl_exception::disabled // disable OTL exceptions
   ); // drop old version of stored procedure, if there is one.

  otl_cursor::direct_exec
   (db,
    "CREATE PROCEDURE my_proc "
    "  @F1 int "
    "AS "
    "SELECT * FROM test_tab "
    "WHERE f1>=@F1 AND f1<=@F1*2 "
   );  // create stored procedure


  insert(); // insert records into table
  select(); // select records from table

 }

 catch(otl_exception& p){ // intercept OTL exceptions
  cerr<<p.msg<<endl; // print out error message
  cerr<<p.stm_text<<endl; // print out SQL that caused the error
  cerr<<p.sqlstate<<endl; // print out SQLSTATE
  cerr<<p.var_info<<endl; // print out the variable that caused the error
 }

 db.logoff(); // disconnect from MS SQL Server

 return 0;

}

Output

====> Starting a fetch sequence....
f1=8, f2=Name8
f1=9, f2=Name9
f1=10, f2=Name10
Cancelling the fetch sequence after 3 rows are fetched
====> Starting another fetch sequence...
f1=4, f2=Name4
f1=5, f2=Name5
f1=6, f2=Name6
f1=7, f2=Name7
f1=8, f2=Name8

Examples ContentsGo Home

Copyright © 1996-2023, Sergei Kuchin, email: skuchin@gmail.com, skuchin@gmail.com .

Permission to use, copy, modify and redistribute this document for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.