in the sql string, changing "concat(nofm, '') as nofm" with "cast(nofm =
as char) as nofm" solved the problem.
What I can't figure out is why this modif which impact on the server, =
solves something that belongs to the client side.

Fran=E7ois

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc [at] m.gmane.o rg

On Fri, Feb 01, 2008 at 09:20:00AM +0100, RAPPAZ Francois wrote:
> in the sql string, changing "concat(nofm, '') as nofm" with "cast(nofm as char) as nofm" solved the problem.
> What I can't figure out is why this modif which impact on the server, solves something that belongs to the client side.

The result of CONCAT() using a numeric literal or field is a binary
string. Just as the result of COMPRESS(), for example, is a binary
string. There's no way for the ODBC driver to know that the first case
really could be a character string as compared to the second.

The issue with the server returning binary strings as the result of
CONCAT() with a numeric literal or field is Bug #12030.

Jim Winstead
MySQL INc.

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org