PEPPLER.ORG
Michael Peppler
Sybase Consulting
Menu
Home
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
Freeware
Sybperl
Sybase::Simple
DBD::Sybase
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
FAQs
Sybase on Linux FAQ
Sybperl FAQ
Personal
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: "WORENKLEIN, David, GCM" <David dot Worenklein at gcm dot com>
Subject: RE: dbrpcsend without dbsqlok
Date: Sep 1 1999 1:26PM

The first was easier to implement, so that's what I did. :-)

But I'll work on the second today.

-----Original Message-----
From: Michael Peppler [mailto:mpeppler@peppler.org]
Sent: Tuesday, August 31, 1999 4:48 PM
To: SybPerl Discussion List
Subject: Re: dbrpcsend without dbsqlok


WORENKLEIN, David, GCM writes:
 > Mike --
 > 
 > In dblib.xs, you say 
 > 
 > 	/* temporay [sic] solution: call dbsqlok() directly after
 > dbrpcsend() */
 > 
 > I think it's time to find a more permanent solution.  I need to call
 > dbrpcsend(), dbpoll() at intervals until something comes back, and then
call
 > dbsqlok().
 > There are two ways to do this that maintain backwards compatibility:
 > 
 >   1. A new function, dbrpcsendnook
 >   2. An optional second parameter, no_dbsqlok.
 > 
 > The second looks better to me.
 > 
 > I've hacked up my 2.10, and I clean up the dbrpcparam list before calling
 > dbsqlok.  I haven't had any problems with it yet, but I haven't purified
my
 > code, either.

I also like the second solution best.

How 'bout sending me your diffs?

Michael
-- 
Michael Peppler         -||-  Data Migrations Inc.
mpeppler@peppler.org    -||-  http://www.mbay.net/~mpeppler
Int. Sybase User Group  -||-  http://www.isug.com
Sybase on Linux mailing list: ase-linux-list@isug.com
**********************************************************************
This e-mail is intended only for the addressee named above.
As this e-mail may contain confidential or privileged information,
if you are not the named addressee, you are not authorised to
retain, read, copy or disseminate this message or any part of it.
************************************************************************