Re: SQL_NO_TOTAL error on text larger than 4096 bytes

But previous version (0.82) does support large text fields without forcing 
users manually check for sql_no_total. Why remove useful and working 
functionality ? Is there a way to put it back ? Or provide a small example how 
to handle it ? I could then use the example to fix my haskell bindings to 
support sql_no_total.


On Monday, May 07, 2012 07:01:03 PM Frediano Ziglio wrote:
> SQL_NO_TOTAL is not an error but a value you should support. It says mainly
> that FreeTDS cannot know the converted length in advance, this for
> performance issues.
> 
> Frediano Ziglio
> 
> Il giorno 07/mag/2012, alle ore 05:42, Vagif Verdi <[email protected]> 
ha scritto:
> > I am using haskell bindings to unixodbc and freetds.
> > They work fine with freetds 0.82 and unixodbc 2.3.0
> > 
> > But upgrade to freetds 0.91 and unixodbc 2.3.1 breakes it. Now it gives me
> > a SQL_NO_TOTAL error on text larger than 4096 bytes.
> > I submitted bug to hdbc-odbc lib here: https://github.com/hdbc/hdbc-
> > odbc/issues/4
> > 
> > I looked through the code of haskell bindings and it does not handle
> > SQL_NO_TOTAL. Just returns an error.
> > 
> > Can anyone tellme what changed either in freetds or in unixodbc to cause
> > it to return SQL_NO_TOTAL instead of just the length of the field ?
> > 
> > Can we bring the old functionality back ? Or if not, how to correctly
> > respond to SQL_NO_TOTAL ?
> > 
> > Regards,
> > Vagif Verdi
> 
> _______________________________________________
> FreeTDS mailing list
> [email protected]
> http://lists.ibiblio.org/mailman/listinfo/freetds