summaryrefslogtreecommitdiff
path: root/mysql-test/main/brackets.result
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-30032: EXPLAIN FORMAT=JSON output: part #2: print 'loops'.Sergei Petrunia2023-02-031-0/+8
|
* MDEV-30032: EXPLAIN FORMAT=JSON output: print costsSergei Petrunia2023-02-031-0/+16
| | | | Basic printout for join and table execution costs.
* MDEV-5215 prerequisite: remove test and test_* database hacks in the test suiteOleksandr Byelkin2022-11-011-2/+0
|
* Merge 10.7 into 10.8Marko Mäkelä2022-04-271-13/+13
|\
| * Merge 10.4 into 10.5Marko Mäkelä2022-04-211-13/+13
| |\
| | * Merge 10.3 into 10.4Marko Mäkelä2022-04-211-13/+13
| | |
* | | MDEV-27036: resolve duplicated key issues of JSON tracing outputs:Sergei Krivonos2021-11-261-60/+92
|/ / | | | | | | | | | | | | | | | | | | | | MDEV-27036: repeated "table" key resolve for print_explain_json MDEV-27036: duplicated keys in best_access_path MDEV-27036: Explain_aggr_filesort::print_json_members: resolve duplicated "filesort" member in Json object MDEV-27036: Explain_basic_join:: print_explain_json_interns fixed start_dups_weedout case for main.explain_json test
* | Merge 10.4 into 10.5Marko Mäkelä2021-03-191-2/+2
|\ \ | |/
| * Merge 10.3 into 10.4Marko Mäkelä2021-03-191-2/+2
| |
* | Merge commit '10.4' into 10.5Oleksandr Byelkin2021-01-061-6/+6
|\ \ | |/
| * Merge branch '10.3' into 10.4bb-10.4-MDEV-23468Oleksandr Byelkin2020-12-251-6/+6
| |
* | MDEV-20632: Recursive CTE cycle detection using CYCLE clause (nonstandard)Oleksandr Byelkin2020-03-101-3/+3
| | | | | | | | Added CYCLE ... RESTRICT (nonstandard) clause to recursive CTE.
* | Merge remote-tracking branch 'origin/10.4' into 10.5Alexander Barkov2019-09-241-1/+4021
|\ \ | |/
| * MDEV-19956 Queries with subqueries containing UNION are not parsedIgor Babaev2019-09-231-1/+4021
| | | | | | | | | | | | | | | | Shift-Reduce conflicts prevented parsing some queries with subqueries that used set operations when the subqueries occurred in expressions or in IN predicands. The grammar rules for query expression were transformed in order to avoid these conflicts. New grammar rules employ an idea taken from MySQL 8.0.
* | MDEV-18844 Implement EXCEPT ALL and INTERSECT ALL operationsWayneXia2019-08-241-1/+1
|/
* MDEV-18689 Simple query with extra brackets stopped workingIgor Babaev2019-05-061-0/+42
| | | | | | | | Parenthesis around table names and derived tables should be allowed in FROM clauses and some other context as it was in earlier versions. Returned test queries that used such parenthesis in 10.3 to their original form. Adjusted test results accordingly.
* MDEV-19363 Assertion `select_lex' failed in LEX::pop_selectIgor Babaev2019-05-011-0/+59
| | | | | | | | This patch corrects the patch for MDEV-19324. The latter did not work properly in the cases when the transformation (SELECT ... ORDER BY ...) LIMIT ... => SELECT ... ORDER BY ... LIMIT ... was applied to the operands of a set operation.
* MDEV-19324 Wrong results from query, using brackets with ORDER BY ..LIMITIgor Babaev2019-04-261-0/+150
| | | | | | | | | | | | | | | | | | | | | | If a select query was of the form (SELECT ... ORDER BY ...) LIMIT ... then in most cases it returned incorrect result. It happened because SELECT ... ORDER BY ... was wrapped into a select with materialized derived table: SELECT ... ORDER BY ... => SELECT * FROM (SELECT ... ORDER BY ...) dt. Yet for any materialized derived table ORDER BY without LIMIT is ignored. This patch resolves the problem by the conversion (SELECT ... ORDER BY ...) LIMIT ... => SELECT ... ORDER BY ... LIMIT ... at the parser stage. Similarly ((SELECT ... UNION ...) ORDER BY ...) LIMIT ... is converted to (SELECT ... UNION ...) ORDER BY ... LIMIT ... This conversion optimizes execution of the query because the result of (SELECT ... UNION ...) ORDER BY ... is not materialized into a temporary table anymore.
* MDEV-16357 LIMIT and ORDER BY clause is ignored on a query with UNIONIgor Babaev2018-11-061-0/+24
| | | | | | when using brackets Do not create master unit for select if it has already one.
* MDEV-16359 wrong result (extra rows) on the query with UNION and bracketsIgor Babaev2018-08-031-0/+12
| | | | | | Due to an obvious bug in st_select_lex_unit::reset_distinct() a union without duplicates of more than 2 selects could return a result set containing duplicate rows if this union was enclosed in ().
* MDEV-11953: support of brackets in UNION/EXCEPT/INTERSECT operationsOleksandr Byelkin2018-07-041-0/+210