FreeTDS Development Group

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

> 
> > From: Wolfgang Gruen
> > Sent: Thursday, January 05, 2006 8:57 AM
> > 
> > I am wondering, is there a new "Release" in the near future and
> > which kind of unit testing is performed to call it a release.
> 
> Freddy, 
> 
> I held off releasing 0.64 because I'm hoping you'll have a fix for the
> results-error-results problem illustrated by my little test 
> (cf. "quick
> ODBC test" December 6-8).  
> 
> If you want me to issue the release without a fix to that problem, I
> will.  I'll just list the problem in "known issues" in the release
> notes.  
> 
> I do releases on weekends and the next couple are booked.  
> Could happen
> later in January.  What do you say?  
> 

Well, current test

On Linux with latest CVS (t return error while t2 return warning)

$ PERL_DL_NONLAZY=1 perl -I./DBD-ODBC-1.13/blib/lib
-I./DBD-ODBC-1.13/blib/arch ./samples/odbc_rpc.pl -D dbi:ODBC:XXX -U
test -P test t
odbc_async_exec is: 0
Binding parameter #1, the return code

Executing: "{? = call t }" with parameters ''
execute returned: '-1'
Result #1:
[FirstResult]
'Here is the first row'
===> state:  msg: This is an example error message.
DBD::ODBC::st fetchrow failed: (DBD: st_fetch/SQLMoreResults err=-1) at
./samples/odbc_rpc.pl line 116.
'Here is the first row'
===> state: 24000 msg: Invalid cursor state
DBD::ODBC::st fetchrow failed: (DBD: st_fetch/SQLFetch err=-1) at
./samples/odbc_rpc.pl line 116.

$ PERL_DL_NONLAZY=1 perl -I./DBD-ODBC-1.13/blib/lib
-I./DBD-ODBC-1.13/blib/arch ./samples/odbc_rpc.pl -D dbi:ODBC:XXX -U
test -P test t2
odbc_async_exec is: 0
Binding parameter #1, the return code

Executing: "{? = call t2 }" with parameters ''
execute returned: '-1'
Result #1:
[FirstResult]
'Here is the first row'
===> state:  msg: This is an example error message.
Result #2:
[LastResult]
'Here is the last row'

On Windows with MS ODBC

>perl odbc_rpc.pl -D dbi:ODBC:XXX -U test -P test t
odbc_async_exec is: 1
Binding parameter #1, the return code

Executing: "{? = call t }" with parameters ''
execute returned: '-1'
Result #1:
[FirstResult]
'Here is the first row'
===> state: 42000 msg: This is an example error message.
DBD::ODBC::st fetchrow failed: (DBD: st_fetch/SQLMoreResults err=-1) at
odbc_rpc.pl line 116.
'Here is the first row'
===> state: HY010 msg: Function sequence error
DBD::ODBC::st fetchrow failed: (DBD: st_fetch/SQLFetch err=-1) at
odbc_rpc.pl line 116.

>perl odbc_rpc.pl -D dbi:ODBC:XXX -U test -P test t2
odbc_async_exec is: 1
Binding parameter #1, the return code

Executing: "{? = call t2 }" with parameters ''
execute returned: '-1'
Result #1:
[FirstResult]
'Here is the first row'
===> state: 01000 msg: This is an example error message.
Result #2:
[LastResult]
'Here is the last row'

You can see that
- some state code are missing
- error for raiserror >= 10 is different ("Invalid cursor state" instead
of "Function sequence error") but similar
- odbc_async_exec is different (0 for FreeTDS 1 for MS ODBC), expected
(we do not support async execute)
- the rest is the same
So, well, I'll fix state (trivial) and I consider the stopover not
existing anymore.

!!!! To sum up: we are ready for 0.64 !!!!

freddy77