FreeTDS Development Group

["David Chang" <dchang AT fsautomation.com>]

James,

Thanks for the update.  At least the behavior is the same as Microsoft 
DB-Library now.  That's the best one can hope for.

In terms of the TDS protocol, I found out that my freetds.conf file is set 
to 8.0.  Do you think if I change it to 4.2 that results processing would be 
any different?  My alternative is to send each stored procedure in its own 
dbsqlexec() which would be much much slower.

DC

----- Original Message ----- 
From: "James K. Lowden" <jklowden AT freetds.org>
To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
Sent: Saturday, October 21, 2006 1:53 PM
Subject: Re: [freetds] dbresults() behavior different between RH7.3 and 
CentOS4


> James K. Lowden wrote:
> > Back in July we had a long discussion on a
> > related topic [cf.
> > https://lists.ibiblio.org/sympa/arc/freetds/2006q3/020266.html].  Your
> > question got me thinking.  How *can* he fetch the return statuses?
>
> I just committed changes to dblib to correct dbresults().  It now returns
> SUCCEED even if a return status is the only result.
>
> Doxygen comments have been updated to reflect "my current thinking" which
> is much closer to Sybase's documentation.  The t0022 unit test has also
> been enhanced to check for this behavior.
>
> No changes were required to libtds, so other APIs aren't affected.  All I
> know for sure is that the db-lib unit tests all pass on a Microsoft
> server.  Testing with bsqldb doesn't show what I expect, but I've run out
> of time.
>
> --jkl
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds