Bug #77460 Remove old-style MAX_STATEMENT_TIME hint (replace with MAX_EXECUTION_TIME)

Submitted: 23 Jun 2015 18:53 Modified: 19 Jul 2015 17:16
Reporter: Gleb Shchepa Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Parser Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any

[23 Jun 2015 18:53] Gleb Shchepa
Description:
The old-style MAX_STATEMENT_TIME hint has been reimplemented by the new-style MAX_EXECUTION_TIME one.
It would be nice to cleanup the code by removing references to the old-style MAX_STATEMENT_TIME hint, at least to eliminate 4 shift/reduce conflicts in the parser.

How to repeat:
N/A
[19 Jul 2015 17:16] Paul DuBois
Noted in 5.7.8 changelog.

The MAX_STATEMENT_TIME option for SELECT statements was removed
because its functionality is now available using the more general
optimizer hint syntax (see ). Statements that begin like this:

SELECT MAX_STATEMENT_TIME = N ...
      
Should be rewritten to begin like this:

SELECT /*+ MAX_EXECUTION_TIME(N) */ ...

There are some minor implementation differences between the two.
MAX_STATEMENT_TIME was not permitted in non-top-level SELECT
statements such as subqueries, or in stored programs, and produced an
error. MAX_EXECUTION_TIME() is permitted in those contexts, but is
ignored.
[27 Aug 2015 4:15] Erlend Dahl
Bug#72540 was marked as a duplicate.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.038 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.