Re: multiple results for a single query: COMPUTE BY clause gives un...

Hi Garrett, 

Thanks for your mail and all the accompanying evidence.
I'll explain a little. 

First off, FreeTDS DOES support COMPUTE clauses, or at least it should.
It looks to me like you've found an issue with the ODBC driver in particular.
>From your evidence, it seems that the code (at least in 0.61) is assuming 
that there will be ROW data after the first RESULT message....

2003-10-29 12:23:18.430175 processing result tokens.  marker is 
81(TDS7_RESULT)
2003-10-29 12:23:18.430239 tds7_get_data_info:1083: 
...( gets the result data)...
...( appears to call ROW token processing...)...
2003-10-29 12:23:18.434549 processing row tokens.  marker is 
88(TDS7_COMPUTE_RESULT)
2003-10-29 12:23:18.434601 inside tds_process_default_tokens() marker 
is88(TDS7_COMPUTE_RESULT)
Unknown marker: 136(88)!!

The ROW token processing doesn't expect or understand the COMPUTE RESULT 
token that it receives.
Maybe it should, but more likely the ROW token processing shouldn't be called 
unless there's ROW data waiting on the stream to be read....


Now, on the "multiple result set" issue. There's a bit of confusion here...

Unfortunately I have to go to work now :-)  I'll explain more when I get 
there.


Bill