Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
3.0.6
-
None
-
Server: FreeBSD 10.3 , MariaDB 10.3.8 Client: Windows 10, ODBC 3.0.6
Description
Might still be a problem with the parsing of the batch.
All examples are executed as a single batch:
Example one:
select 1; |
select 1; |
This does deliver the right results.
Example two:
SELECT * from DB.mytable;
|
SELECT 1; |
This does deliver all the rows from mytable and the 1 at the end. Works.
Example three:
SELECT 1; |
SELECT * FROM DB.mytable;
|
This does deliver the first result "1" and after that a "AccessViolationException" gets returned.
Example four:
SELECT * FROM DB.mytable;
|
SELECT * FROM DB.mytable;
|
The first SELECT delivers the right results, but the 2nd SELECT returns only the correct amount of rows but they are empty and trigger a NumberFormatException. Fields with INT datatype do work somehow.
A similar result with data from the information_schema is returned by these queries:
CREATE TEMPORARY TABLE _temp_statistics AS (SELECT * FROM INFORMATION_SCHEMA.STATISTICS WHERE TABLE_SCHEMA = "DB"); |
SELECT * FROM _temp_statistics;
|
or
DROP TABLE IF EXISTS _temp_statistics;
|
SELECT * FROM INFORMATION_SCHEMA.STATISTICS;
|
These statements do work with the mysql ODBC driver or executed on their own.