Re: myODBC 3.51.10, mySQL 4.1.8, UTF-8 and protocol issue ?

[HMax]

"It could be" : too bad is not "It's probably it" :/
Except by trying to connect with another connector supporting Binary
protocol, is there a way to verify this ? Any bêta or even Alpha
version of myODBC 3.53 with Binary protocol available ? This problem
is sort of blocking us for the moment, at least if we are not sure
it's the source of our problem.

Thx, Chehax


On Mon, 10 Jan 2005 20:09:11 -0800, Peter Harvey <pharvey@stripped> wrote:
> HMax wrote:
> 
> >Hi List,
> >
> >myODBC version: 3.51.10-1
> >mySQL version : 4.18-nt
> >
> >We are having issue with a few fields from a 9millions big database
> >and we suspect myODBC to be the source of the
> >problem for the following reason.
> >
> >We use myODBC in ASP and we when we just display the values with
> >error, in an UTF-8 encoded page, only some of the
> >characters are not displayed correctly, with ?? in place of the
> >correct value. Like "Hello W??rld" for instance.
> >However, when we do the same query and look at the result in mySQL
> >Query Browser, the value is displayed correctly. The
> >datas in the table are imported from a text file using the LOAD DATA
> >INFILE command. The server, database, and all
> >fields character set is UTF-8, always.
> >
> >Our idea, after some research, is that mySQL Query Browser might use
> >the new binary protocol, whereas myODBC does notfor
> >sure. Our question is : could this be it, and what should we do if it is ?
> >
> >Thank you for your help!
> >CheHax
> >
> >
> >
> Yes; it could be. MyODBC 3.53 will use all of the latest features. We
> are working on a 3.53 release but have not definitive release date.
> 
> --
> Peter Harvey, Software Developer
> MySQL AB, www.mysql.com
> 
> Are you MySQL certified?  www.mysql.com/certification
> 
> 


-- 
HMax