Subject | Re: [firebird-support] Strange API string truncation error |
---|---|
Author | Richard Wesley |
Post date | 2007-05-11T18:46:22Z |
On May 11, 2007, at 11:32, Ivan Prenosil wrote:
Yes, I was wondering about that. I had just switched in the 2.0 ODBC
driver as the transport layer and it worked, but the connection
charset was set to UNICODE_FSS not UTF8. When I set it to UFT8, the
problem occured with the ODBC driver as well.
I noticed some traffic about UTF8 as a connection character set a
while back, so is this a known problem? And if so:
- Is it in the client or the server?
- Has it been fixed in 2.0.1?
TIA,
________________________________________________________
Richard Wesley Senior Software Developer Tableau
Software
Visit: http://www.trytableau.com/now.html
> Sorry, I overlooked it. But I think you did not try the same thing:(I'm impressed that you remember!)
> Your application uses UTF8 connection charset, while ISQL does not,
> right ?
Yes, I was wondering about that. I had just switched in the 2.0 ODBC
driver as the transport layer and it worked, but the connection
charset was set to UNICODE_FSS not UTF8. When I set it to UFT8, the
problem occured with the ODBC driver as well.
I noticed some traffic about UTF8 as a connection character set a
while back, so is this a known problem? And if so:
- Is it in the client or the server?
- Has it been fixed in 2.0.1?
TIA,
________________________________________________________
Richard Wesley Senior Software Developer Tableau
Software
Visit: http://www.trytableau.com/now.html