Bug #92774 Bug with select * using myODBC 8
Submitted: 13 Oct 2018 8:51 Modified: 21 May 15:35
Reporter: Jernej Pecjak Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:8 OS:Microsoft Windows (server 2016)
Assigned to: CPU Architecture:x86

[13 Oct 2018 8:51] Jernej Pecjak
Description:
Using prepared statements in classic ASP the select * doesn't work, says that the EOF is met (no records).

How to repeat:
Make any table that has more than one field and more than one column in mySQL and use this:

MM_test_STRING="Provider=MSDASQL;Driver={MySQL ODBC 8.0 Unicode Driver};server=localhost;uid=test;pwd=test;database=test;OPTION=16384;"
Set rsTest_cmd= Server.CreateObject ("ADODB.Command")
rsTest.ActiveConnection = MM_test_STRING
rsTest.CommandText = "select * from test where ID=1" 
rsTest.Prepared = true

Set rsTest = rsTest _cmd.Execute
rsObiskovalec_numRows = 0

response.write(rsTest("ID"))

if you use SELECT ID FROM TEST it works
[13 Oct 2018 8:53] Jernej Pecjak
I can not edit what I wrote, the correct line:

rsTest_numRows = 0

instead of

rsObiskovalec_numRows = 0
[13 Oct 2018 9:57] Jernej Pecjak
As it seems the bug started with 5.3.11 version of myODBC, the 5.3.10 works well on the same page.
[15 Oct 2018 8:41] Miguel Solorzano
Thank you for the bug report. I couldn't repeat with my own test case, please provide a test case like did the reporter of bug: https://bugs.mysql.com/bug.php?id=92078 (create table, insert data, complete code to run, etc). Thanks in advance.
[16 Nov 2018 1: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".
[21 May 13:58] Jernej Pecjak
This bug seems fixed in 5.3.13
[21 May 14:16] Miguel Solorzano
Then according your prior comment, it could be closed?.
[21 May 14:33] Jernej Pecjak
And in 8.0.16 also!
[21 May 15:30] Jernej Pecjak
Yes it can be closed. I can not find in the changelog that this specific problem is fixed but it seem to be.
[21 May 15:35] Miguel Solorzano
Thank you for the feedback.