FreeTDS Development Group

["James K. Lowden" <jklowden AT freetds.org>]

blackwater dev wrote:
> When I set the version to 7.0, I get no errors unless I try to select a
> datetime field and this is from my Dump.  I do have client
> charset=UTF-8. When I change the version to 8 for the 2000 box, I get
> all the conversion errors below.
...
> 13:41:02.574077 Starting log file for FreeTDS 0.63
>         on 2006-04-12 13:41:02 with debug level 99.
> 13:41:02.575377 names for ISO-8859-1: ISO-8859-1
> 13:41:02.575525 names for UTF-8: UTF-8
> 13:41:02.575655 names for UCS-2LE: UCS-2LE
> 13:41:02.575786 names for UCS-2BE: UCS-2BE
> 13:41:02.575933 iconv to convert client-side data to the "UTF-8"
> character set
> 13:41:02.576228 tds_iconv_info_init: converting "UTF-8"->"UCS-2LE"
> 13:41:02.576491 tds_iconv_info_init: converting "ISO-8859-1"->"UCS-2LE"
> 13:41:02.576712 Connecting to 207.76.168.21 port 1433, TDS 7.0.
> 
> 
> Warning: mssql_query(): iconv E2BIG: Error converting between character
> sets. Output buffer exhausted. (severity 16) in
> /usr/local/apache2/htdocs/nh/includes/lib/ms_db.class.php on line 182

OK.  You're using UTF-8, it's true.  The error is E2BIG, indicating that
the output buffer isn't large enough to hold the the converted characters.
 However, that error can't be induced by selecting a datetime field.  The
UTF-8 and ASCII forms of date strings are identical: identical in length,
identical in data.  So the error isn't quite where you think it is.  IMHO,
of course.  

Could you please try this query:

        SELECT getdate() as 'today'

I think that will work.  If not, please post the log.  

ISTR you had some kind of blob you were fetching.  I think the problem may
be in there somewhere, perhaps trying to convert your image data to a hex
string.  See if you can't isolate the column that is causing the problem. 
Give us a log of that and then let's see what's what.  

HTH.

--jkl