Re: How to Turn Off Character Conversion Failed Warnings
Frediano Ziglio <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <[email protected]> |
2010/11/15 Eli Finkelshteyn <[email protected]>: > Hi David, > Unless I'm missing something, this seems like the same advice I've seen in > other places. It's not helpful to me because I'm already using "Client > Charset = UTF-8." This does not, and should not solve my problem as this can > only convert characters into UTF-8 that are correctly encoded in the > database. In my case-- and this is my main problem-- I have a char field > (note: chars are supposed to hold ASCII characters and nothing else) that > has cp1252 inserted into it. Because of this, when FreeTDS grabs data from > that field, assumes it's ASCII, and tries to convert it to UTF-8, it blows > up since some of those cp1252 code points don't exist in UTF-8 (i.e. code > point 253-- a y with an accent sign-- among others). > No, FreeTDS does not assume the server encoding (at least not on mssql), it KNOWS the server encoding. Perhaps you are using a non patched version which doesn't detect correctly cp1252 (using iso8859-1 instead). freddy77 _______________________________________________ FreeTDS mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/freetds