Bug #72331 | MAX_STATEMENT_TIME does not respond when using cursor fetch | ||
---|---|---|---|
Submitted: | 13 Apr 2014 16:42 | Modified: | 28 Jan 2022 12:05 |
Reporter: | Sadao Hiratsuka | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 5.7.4, 5.7.5 | OS: | Any |
Assigned to: | Filipe Silva | CPU Architecture: | Any |
Tags: | max_statement_time |
[13 Apr 2014 16:42]
Sadao Hiratsuka
[15 Apr 2014 19:28]
Sveta Smirnova
Thank you for the report. Verified as described.
[15 Apr 2014 19:29]
Sveta Smirnova
test case for Java 1.6 or older
Attachment: bug72331.java (text/x-java), 954 bytes.
[29 Dec 2015 13:22]
Filipe Silva
Posted by developer: The option MAX_STATEMENT_TIME=n is deprecated MySQL 5.7.8 but the same issue is observed when using the hint /*+ MAX_EXECUTION_TIME(1) */ that replaces it.
[28 Jan 2022 12:05]
Alexander Soklakov
Posted by developer: This bug is not reproducible with the latest Connector/J 8.0. Connector/J 5.1 series came to EOL on Feb 9th, 2021, see https://www.mysql.com/support/eol-notice.html, so this bug will not be fixed there.