Bug #7465 Problem in SELECT - COUNT
Submitted: 21 Dec 2004 21:05 Modified: 30 May 2013 12:24
Reporter: Michal Merta Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:4.1.8 OS:Linux (LINUX)
Assigned to: CPU Architecture:Any

[21 Dec 2004 21:05] Michal Merta
Description:
Dears,

I'm a developer of the MS VISUAL FOXPRO applications. I use database MySQL on LINUX system.
I always used database MySQL without problems. But after migration to database MySQL 4.1.8, I found that the BUG.

EXAMPLE CODE:
MS Visual Foxpro 8, MS Windows XP SR-1

=SQLEXEC(_handle,"SELECT COUNT(*) AS _temp_count FROM tables1 WHERE id=1","_cursor1")

? type("_cursor1._temp_count")  && return format of the variable

result format:

CHARACTER !!!! No NUMERIC !!!

I usually got the result in the NUMERIC format, but now I got the result in the CHARACTER format. Where is the error ?
I use the MS Visual FOXPRO same 6 month. Only the version of MySQL was changed. From 4.0.XX to 4.1.8.

Michal Merta Ing., MBA
Freyova 27/82
Prague
Europe
e-mail: michal.merta@jobman.cz
ICQ: 46-397-034

How to repeat:
ALWAYS

Suggested fix:
modify the result from CHARACTER TO NUMERIC type, like it was once.
[22 Dec 2004 1:00] Hartmut Holzgraefe
when trying this with PHP against a 4.1.8 server i get the field type reported as "int" just fine.
looks like this is actualy sort of an ODBC specific problem so i'm changing the category to Connector/ODBC for now
[22 Dec 2004 1:26] Michal Merta
I don't know if your change is correct, because I used MyODBC 3.51.06. Olny the version of MySQL was changed. Is it possible, that the MySQL 4.1.8. changed some characteristic for communication via MyODBC ?
[3 Jan 2005 13:53] Michal Merta
I don't see any diferrence between OLD and new situactiom

M.Merta
[6 Feb 2005 3:43] MySQL Verification Team
I tested this using Access 2003 and Connector/ODBC 3.51.9
(the version 3.51.10 currently has problem for to connect with
it) and I got numeric type. However the main difference is that
the drivers 3.51.9 and above were compiled against the
4.0.XX client library and maybe it is affecting the behavior
of Fox Pro, so please wait for the next release of 3.51.11
and test again and report for us the test's results.
Sorry I don't have FoxPro for to test at my side.
Thanks in advance
[7 Mar 2005 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[30 May 2013 12:24] Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.