Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: Jamie Belanger <jamie_belanger at globalcrossing dot com>
Subject: RE: DBlib phased out?
Date: Mar 8 2000 4:20PM

This may be overly simplistic, but it's very easy to just store the SQL
command that you're using in a variable. I exclusively use CTlib, and simply
place my commands in $SQL1, $SQL2, etc. 

It basically serves the same purpose as a buffer without being dependant
upon the CTlib module itself. (or perhaps not ;)

Jamie Belanger
Sys Admin, Global Crossing
(319) 298-1489 or ext. 489 

-----Original Message-----
From: Michael Peppler []
Sent: Wednesday, March 08, 2000 9:16 AM
To: SybPerl Discussion List
Subject: Re: DBlib phased out?

Arthur Goldstein writes:
 > The key reason I used db-lib over ct-lib was that db-lib stored the
 > buffer that could show what sql was being sent to the database.  I
 > could not figure out a way to do that in ct-lib.  Does ct-lib have
 > a method for that?


You could handle this on the client by overloading the ct_command()
and/or ct_execute() calls to store the command buffer in the $dbh for
later retrieval.

(and maybe Sybase::CTlib could be modified to do this for you...)

Michael Peppler         -||-  Data Migrations Inc.    -||-
Int. Sybase User Group  -||-
Sybase on Linux mailing list: