FreeTDS Development Group

[Brian Bruns <camber AT umcc.ais.org>]

Strange, I would expected to have seen an error returned to dberrhandler.
It really sounds like token.c is out of date?!? But, given that it was a
fresh machine I don't see how that could be. You might try setting a
breakpoint in tds_submit_query() and printing the value of
tds->res_info->state.  On the second call it should be TDS_PENDING (1 I
think), and then step through and make sure it calls tds_client_msg() and
returns TDS_FAIL.



On Wed, 13 Jan 1999, Craig Spannring wrote:

> 
> 
> I just grabbed on fresh copy and compiled it on a fresh machine.
> t0004 and t0005 still fail for me.  
> 
> The last few lines of output from t0005 is-
> 
> Read a row of data -> 42 row 0042  
> Read a row of data -> 43 row 0043  
> Read a row of data -> 44 row 0044  
> Read a row of data -> 45 row 0045  
> Read a row of data -> 46 row 0046  
> Read a row of data -> 47 row 0047  
> Read a row of data -> 48 row 0048  
> Read a row of data -> 49 row 0049  
> select * from dblib0005 where i>950 order by i
> t0005.c:207: dbsqlexec should have failed but didn't
> dblib failed! on t0005.c
> 
> 
> Does anyone else get failures on t0004 and t0005?
> 
> 
> Brian Bruns writes:
>  > 
>  > 
>  > On Wed, 13 Jan 1999, Brian Bruns wrote:
>  > 
>  > > Hrmmm....My results:
>  > > 
>  > 
>  > Sorry to followup my own post, but...I've tested t0004 and t0005 on BSDI
>  > (which meant doing a fresh checkout from CVS) and they worked.  So, its
>  > not a matter of missing a checkin. *shrug again*
> 
>