MySQL Bugs: #99712: server variable max_execution

Bug #99712	server variable max_execution_time now set in ODBC driver
Submitted:	27 May 2020 19:19	Modified:	29 Jul 2020 19:48
Reporter:	Alex Miller	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	5.3.14	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	ODBC

Description:
On previous versions of MySQL ODBC driver (5.3.4 for example) there was no max_execution_time value set for session or global when connecting to a MYSQL linked server in MSSQL

Select * from openquery(linkserver, 'select @@max_execution_time, @@global.max_execution_time')

@@max_execution_time	@@global.max_execution_time
0	                0

After updating to the latest ODBC drivers 5.3.14, there's a value set for both

Select * from openquery(linkserver, 'select @@max_execution_time, @@global.max_execution_time')

@@max_execution_time	@@global.max_execution_time
600000	                7200000

MySQL @@version
5.7.29-enterprise-commercial-advanced-log

How to repeat:
Under 5.3.4

Select * from openquery(linkserver, 'select @@max_execution_time, @@global.max_execution_time')

@@max_execution_time	@@global.max_execution_time
0	                0

updated to 5.3.14

Select * from openquery(linkserver, 'select @@max_execution_time, @@global.max_execution_time')

@@max_execution_time	@@global.max_execution_time
600000	                7200000

Thank you for the bug report. Which server version are you connected to?

select @@version
5.7.29-enterprise-commercial-advanced-log

Tool to connect/query MySQL 5.7.32 with 5.3.14 DSN ODBC Connector

Attachment: 99712_1.png (image/png, text), 173.58 KiB.

Checking result 0, 0 select @@max_execution_time, @@global.max_execution_time

Attachment: 99712_2.png (image/png, text), 65.57 KiB.

Thank you for the feedback. To check the issue I used the Microsoft tool odbcte32 you can see the prior attached screenshot it returns 0, 0.