Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
3.0.3
-
MariaDB 10.2.13 on FreeBSD 11.1, ODBC Connector 3.0.3 on Windows 10 Client
Description
Using compression in a DSN for the MariaDB ODBC Driver, causes the application to wait idefinitly for the query execution.
Example code to reproduce:
System.Data.Odbc.OdbcConnection dbConnection = new System.Data.Odbc.OdbcConnection(); |
System.Data.Odbc.OdbcCommand dbCommand;
|
dbConnection.ConnectionString = "Driver={MariaDB ODBC 3.0 Driver};Server=mariadb-dev;Database=TESTDB;User=TEST;Password=TEST;Option=2048"; |
|
dbConnection.Open();
|
dbCommand = dbConnection.CreateCommand();
|
dbCommand.CommandText = "SELECT DISTINCT SCHEMA_NAME AS CATALOG_NAME FROM INFORMATION_SCHEMA.SCHEMATA"; |
int result = dbCommand.ExecuteNonQuery(); |
Compression works on the 10.2.13 server using mysqlclient.
If you remove "Option=2048" from the DSN the query returns a result.
A "select 1" (with compression set) returns ERROR [08S01] [ma-3.0.3][10.2.13-MariaDB-log]Unknown command‘
The above code works with MariaDB 10.1.31 / ODBC 3.0.3 / with compression set.
Is there a compatibility issue with ODBC 3.0.3 and MariaDB 10.2 ?
I can provide any further necessary information.
Attachments
Issue Links
- is caused by
-
CONC-323 mariadb_stmt_execute_direct hangs forever if compression used
- Closed