FreeTDS Development Group

["ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>]

> 
> ZIGLIO, Frediano, VF-IT wrote:
> > I still have some things to do before a release
> > 1- odbc cursors, sybase
> > 2- odbc cursors, update
> > 3- timeout
> 
> Hi Freddy, 
> 
> I really think resultset handling is the most important ODBC 
> problem.  I
> haven't been able to work on it, but it really needs to be done and it
> would be great if you took it on.[1]  
> 
> If you don't want to -- or if you don't like the way I described it --
> that's OK, too.  For me, though, it's the *only* thing we 
> need for 0.65.  
> 
> We need a tds_read_results() function in src/tds/api.c ;-) that reads
> *everything* after the last ROW token (if there is one) up to the next
> result (if any).  That way, the client app can pull the extra bits --
> COMPUTE, RETURN_STATUS, etc. -- in any order he wants to from the ODBC
> layer.  
> 
> To write that function correctly, we need to deal with server messages
> (and some client messages).  Message handling has been a 
> problem in ODBC
> from the beginning.  :-(  I think this is the only way to fix it.  
> 

8-| I never though this was a "problem"... currently is not "broken" but
perhaps "ugly".
ODBC read as much as it can like proprietary implementations. The
problem is that code is in ODBC and not in libTDS so dblib is not that
perfect as ODBC (I don't know ctlib that much...).

Frediano