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: "Delegal, Darin" <ddelegal at citistreetonline dot com>
Subject: RE: :Sybase - differences between 1.05 and 1.04
Date: Jun 1 2005 4:40PM

I believe that the ct_send error is caused by still having results in
the buffer from the previous command. You probably need to loop on the
outputs until you get a "no more results" on the ct_results call.

Darin Delegal 
Senior Software Developer 
CitiStreet - Quadrant 2, #4-209 
(904) 594-0286, (904) 594-0039 fax 
'When the customer demands the impossible, they will end 
up buying from the guy who offers them the impossible. 
And the results, though tragic, are sadly predictable.' - Robert A.



From: []
On Behalf Of Peter Sinnott
Sent: Wednesday, June 01, 2005 11:58 AM
To: syb perl
Cc: Peter Sinnott
Subject: DBD::Sybase - differences between 1.05 and 1.04

  I am getting the following error/warning messages when a stored 
procedure call fails. 

Message String: ct_send(): user api layer: external error: This routine 
cannot be called because another command structure has results pending 

Message String: ct_cmd_drop(): user api layer: external error: This 
routine cannot be called while results are pending for a command that 
has been sent to the server. 

These messages are displayed with DBD::Sybase 1.05 but not with 1.04. 

Are they anything I should be worried about?  

The program in question connects to multiple databases and performs 
a combination of select and inserts/updates via stored procedures. 
I have reduced it to a test case that connects to 1 database and 
no longer performs selects so I am not sure what pending results are 
being referred to. 

Possibly this is related to the chained transactions/autocommit changes 
in 1.05? 


We seamlessly network economically sound content so that we may
coordinate competitive meta-services while promoting personal employee