[freetds] 0.65 (or whatever) TODO

ZIGLIO, Frediano, VF-IT Frediano.Ziglio at vodafone.com
Mon Apr 16 04:01:59 EDT 2007


> > 
> > The 'goodbye' message was lost.  Is this an isql problem, too?  
> > 
> > Thanks for fixing bsqlodbc and for explaining the reversed 
> messages in
> > unixODBC's isql.  If the lost messages are an isql bug, too, and if
> > bsqlodbc behaves well with Sybase's driver, then I'm happy to 
> > prepare to
> > release 0.65.  
> > 
> 
> Watchnig again log I realize that the problem seems in DM too... from
> log:
> 
> [ODBC][32028][SQLExecute.c][344]
>                 Exit:[SQL_SUCCESS_WITH_INFO]
>                 DIAG [01000] [FreeTDS][SQL Server]hello
>                 DIAG [01000] [FreeTDS][SQL Server]goodbye
> 
> so DM read errors in the correct order however
> 
> [ODBC][32028][SQLError.c][342]
>                 Entry:
>                         Statement = 0x8a8b978
>                         SQLState = 0xbf8c08fe
>                         Native = 0xbf8c0700
>                         Message Text = 0xbf8c0709
>                         Buffer Length = 500
>                         Text Len Ptr = 0xbf8c0706
> [ODBC][32028][SQLError.c][379]
>                 Exit:[SQL_SUCCESS]
>                         SQLState = 01000
>                         Native = 0xbf8c0700 -> 0
>                         Message Text = [[unixODBC][FreeTDS][SQL
> Server]goodbye]
> [ODBC][32028][SQLError.c][342]
>                 Entry:
>                         Statement = 0x8a8b978
>                         SQLState = 0xbf8c08fe
>                         Native = 0xbf8c0700
>                         Message Text = 0xbf8c0709
>                         Buffer Length = 500
>                         Text Len Ptr = 0xbf8c0706
> [ODBC][32028][SQLError.c][379]
>                 Exit:[SQL_SUCCESS]
>                         SQLState = 01000
>                         Native = 0xbf8c0700 -> 0
>                         Message Text = [[unixODBC][FreeTDS][SQL
> Server]hello]
> [ODBC][32028][SQLError.c][342]
>                 Entry:
>                         Statement = 0x8a8b978
>                         SQLState = 0xbf8c08fe
>                         Native = 0xbf8c0700
>                         Message Text = 0xbf8c0709
>                         Buffer Length = 500
>                         Text Len Ptr = 0xbf8c0706
> [ODBC][32028][SQLError.c][379]
>                 Exit:[SQL_NO_DATA]
> [ODBC][32028][SQLError.c][424]
>                 Entry:
>                         Connection = 0x8a30130
>                         SQLState = 0xbf8c08fe
>                         Native = 0xbf8c0700
>                         Message Text = 0xbf8c0709
>                         Buffer Length = 500
>                         Text Len Ptr = 0xbf8c0706
> [ODBC][32028][SQLError.c][461]
>                 Exit:[SQL_NO_DATA]
> 
> so SQLError return errors in the wrong order :(. I'll look at unixODBC
> source.

???? I can't believe it... unixODBC sort errors alphabetically !!!

so "goodbye" < "hello"..

See check_error_order in DriverManager/__info.c (called by
insert_into_error_list).
This in both 2.2.11 and 2.2.12!

freddy77



More information about the FreeTDS mailing list