[ODBC-139] Compression causes queries to never respond / fail. Created: 2018-03-09  Updated: 2018-04-20  Resolved: 2018-04-20

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: 3.0.3
Fix Version/s: 3.0.4

Type: Bug Priority: Major
Reporter: Patrick Dudziak Assignee: Lawrin Novitsky
Resolution: Fixed Votes: 0
Labels: Compatibility
Environment:

MariaDB 10.2.13 on FreeBSD 11.1, ODBC Connector 3.0.3 on Windows 10 Client


Issue Links:
Problem/Incident
is caused by CONC-323 mariadb_stmt_execute_direct hangs for... Closed

 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.



 Comments   
Comment by Lawrin Novitsky [ 2018-03-16 ]

Thanks for your report. I have verified the issue, it is easily reproducible.

But looks like that is bug in the underlying Connector/C or in the server. I will link to this issue the new report of the bug causing this one.

Comment by Lawrin Novitsky [ 2018-04-20 ]

The causing C/C bug has been fixed

Generated at Thu Feb 08 03:26:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.