FreeTDS Development Group

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

> 
> Jeff Dahl wrote:
> > Luke Benstead wrote:
> > > It looks as though I'm not the only one who has experienced this:
> > >
> > > https://lists.ibiblio.org/sympa/arc/freetds/2006q1/019851.html
> > > 
> http://archives.devshed.com/forums/development-94/warning-retu
> rn-as-copy-of-last-result-row-was-warning-1897372.html
> > >   
> > I believe this was fixed with v0.64.
> 
> Indeed. It's definitely solved in the current snapshot:
> 
> $ echo 'select max(a) as foo from (select cast(null as int) 
> as a) as test'
> | bsqlodbc -S$S -U$U -P$P
>        foo
> ----------
>       NULL
> bsqlodbc: error 8153: 01003: [FreeTDS][SQL Server]Warning: 
> Null value is
> eliminated by an aggregate or other SET operation.
> 
> I wrote bsqlodbc because so many ODBC questions arise in complex
> environments with FreeTDS somewhere in the middle.  Try your 
> query with
> it.  If if fails, you have a FreeTDS problem.  If it 
> succeeds, you *might*
> have a FreeTDS problem, but it manifests itself at higher 
> elevations.  
> 
> HTH.  
> 

Well... I added warning test (src/odbc/unitests) just adding test from
Hohm, see 
http://freetds.cvs.sourceforge.net/freetds/freetds/src/odbc/unittests/wa
rning.c?revision=1.5&view=markup
today I added also Jeff Dahl query. Result at 
http://freetds.sourceforge.net/out/test/odbc_warning.1.html
(I did a small error for Sybase but on my test machine is working
correctly)

freddy77