FreeTDS Development Group

[Paul Rensing <prensing AT cimetrics.com>]

James,

Thanks for replying, but unfortunately, it did not help. I updated to
last night's snapshot, but I am still getting the problem.

I suspect that you are right that it is not getting the metadata.
However, AFAIK, my queries are returning data.

I modified my code a little to get more info. In the case you cited, the
Python "description" table reports a single column (there should be 3)
with an empty description. Specifically it reports:
 name ''
 type_code 2
 display_size 0
 internal_size 4
 precision 0
 scale 0
 null_ok 0

Is it possible that this same bug exists in a different code path?

        Paul

On Mon, 2003-03-17 at 10:56, Lowden, James K wrote:
> > From: Paul Rensing [mailto:paul.rensing AT att.net]
> > Sent: March 17, 2003 10:26 AM
> > 
> > I recently upgraded FreeTDS and the Python driver (Sybase.py) and now,
> > my interactions with MSSql are flakey. 
> [...] 
> >  - Throughout my script, I read through various tables (pretty simple
> > select statement). On starting the query, I loop over the column
> > information to get the names. Sometimes, this array is empty.
> 
> Nothing in your description makes me suspect your DBA's changes.  
> 
> Theory: Sybase.py uses ct-lib, and sometimes your select statement returns
> no rows.  
> 
> If so, see LJ Bayuk's message of Sunday.  Queries returning empty result
> sets in 0.61 fail to return column metadata.  This is fixed in CVS.  
> 
> If that sounds like we're in the right territory, please upgrade to the
> nightly snapshot and tell us how you fare.  Else I can make another guess?  
> 
> --jkl
> 
> 
> The information contained in this transmission may contain privileged and
> confidential information and is intended only for the use of the person(s)
> named above.  If you are not the intended recipient, or an employee or agent
> responsible for delivering this message to the intended recipient, any
> review, dissemination, distribution or duplication of this communication is
> strictly prohibited. If you are not the intended recipient, please contact
> the sender immediately by reply e-mail and destroy all copies of the
> original message. Please note that we do not accept account orders and/or
> instructions by e-mail, and therefore will not be responsible for carrying
> out such orders and/or instructions.
> 
> 
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
-- 
Paul Rensing <prensing AT cimetrics.com>
Cimetrics, Inc.