An error occurred fetching the project authors.
- 06 Apr, 2017 1 commit
-
-
Igor Babaev authored
When a CTE referring to another CTE from the same with clause was used twice then the server could not find the second CTE and reported a bogus error message. This happened because for any unit that was created as a clone of a CTE specification the pointer to the WITH clause that owned this CTE was not set.
-
- 27 Mar, 2017 1 commit
-
-
Igor Babaev authored
The method With_element::check_unrestricted_recursive() icorrectly performed the check that no recursive reference is not encountered in inner parts of outer joins. As a result the server reported errors for valid specifications with outer joins.
-
- 08 Mar, 2017 1 commit
-
-
Igor Babaev authored
The bug was caused by a wrong order of statements in With_clause::print(). As a result any view definition containing WITH clause with several CTE specifications was put the frm file in a syntactically incorrect form.
-
- 10 Feb, 2017 1 commit
-
-
Nirbhay Choubey authored
-
- 19 Jan, 2017 1 commit
-
-
Igor Babaev authored
When a query containing a WITH clause is printed by EXPLAIN EXTENDED command there should not be any data expansion in the query specifications of the WITH elements of this WITH clause.
-
- 13 Nov, 2016 1 commit
-
-
Igor Babaev authored
If a recursive CTE referred to a materialized view/derived table then the query that used this CTE returned a bogus error message.
-
- 01 Oct, 2016 1 commit
-
-
Igor Babaev authored
The code for st_select_lex::find_table_def_in_with_clauses() did not take into account the fact that the specs for mergeable CTEs were cloned and were not processed by the function With_element::check_dependencies_in_spec().
-
- 26 Sep, 2016 1 commit
-
-
Igor Babaev authored
The bug was in the code of the recursive method With_element::check_unrestricted_recursive. For recursive calls of this method sel->get_with_element()->owner != owner.
-
- 06 Sep, 2016 1 commit
-
-
Igor Babaev authored
The bug manifested itself for recursive definitions that used anchors over tables with blobs.
-
- 30 Aug, 2016 1 commit
-
-
Igor Babaev authored
Added comments. Added reaction for exceeding maximum number of elements in with clause. Added a test case to check this reaction. Added a test case where the specification of a recursive table uses two non-recursive with tables.
-
- 26 Aug, 2016 1 commit
-
-
Igor Babaev authored
Added comments.
-
- 27 Jul, 2016 1 commit
-
-
Igor Babaev authored
Temporary tables created for recursive CTE were instantiated at the prepare phase. As a result these temporary tables missed indexes for look-ups and optimizer could not use them.
-
- 30 Jun, 2016 1 commit
-
-
Igor Babaev authored
-
- 26 Jun, 2016 1 commit
-
-
Igor Babaev authored
-
- 24 May, 2016 1 commit
-
-
Galina Shalygina authored
Added test cases to check the fix. Fixed the problem of wrong types of recursive tables when the type of anchor part does not coincide with the type of recursive part. Prevented usage of marerialization and subquery cache for subqueries with recursive references. Introduced system variables 'max_recursion_level'. Added a test case to test usage of this variable.
-
- 19 May, 2016 1 commit
-
-
Galina Shalygina authored
Added the check whether there are set functions in the specifications of recursive CTE. Added the check whether there are recursive references in subqueries. Introduced boolean system variable 'standards_compliant_cte'. By default it's set to 'on'. When it's set to 'off' non-standard compliant CTE can be executed.
-
- 14 May, 2016 1 commit
-
-
Galina Shalygina authored
Fixed a bug that caused crashes for SHOW CREATE VIEW <view> when <view> was recursive. Added a test case to check the fix.
-
- 12 May, 2016 1 commit
-
-
Galina Shalygina authored
-
- 09 May, 2016 1 commit
-
-
Galina Shalygina authored
-
- 08 May, 2016 1 commit
-
-
Galina Shalygina authored
-
- 20 Apr, 2016 1 commit
-
-
Igor Babaev authored
When the specification of a WITH table referred to a view that used a based table with the same name as the WITH table the server went into an infinite loop because it erroneously resolved the reference to the base table as the reference to the WITH table. With tables used in a view cannot be searched for beyond the scope the view.
-
- 19 Apr, 2016 1 commit
-
-
Igor Babaev authored
When the specification of a WITH table referred to a view that used a based table with the same name as the WITH table the server went into an infinite loop because it erroneously resolved the reference to the base table as the reference to the WITH table. With tables used in a view cannot be searched for beyond the scope the view.
-
- 17 Feb, 2016 1 commit
-
-
Igor Babaev authored
of mdev-8789. Fixed a bug in TABLE_LIST::print. Fixed another bug for the case when the definition of a WITH table contained column list while the join in the main query used two instances of this table.
-
- 21 Dec, 2015 1 commit
-
-
Igor Babaev authored
-
- 18 Dec, 2015 1 commit
-
-
Galina Shalygina authored
Initial implementation
-