- 07 Nov, 2017 1 commit
-
-
Alexander Barkov authored
-
- 05 Nov, 2017 1 commit
-
-
Igor Babaev authored
Conversion of NOT IN predicates into NOT IN subqueries did not work correctly: the predicates actually were converted into IN subqueries. As a result if the conversion was applied for the query with a NOT IN predicate the query could return a wrong result set.
-
- 04 Nov, 2017 4 commits
-
-
Marko Mäkelä authored
-
Igor Babaev authored
-
Igor Babaev authored
the system variable @@in_subquery_conversion_threshold
-
Igor Babaev authored
-
- 03 Nov, 2017 1 commit
-
-
Igor Babaev authored
-
- 02 Nov, 2017 11 commits
-
-
Alexander Barkov authored
-
Alexander Barkov authored
Adding missing commands into sql_yacc_ora.yy: %token VALUES_IN_SYM %token VALUES_LESS_SYM and their parser hacks with Select->parsing_place. Note: the grammar for table_value_constructor will be merged later separately.
-
Marko Mäkelä authored
Ideally, we would move some code from ha_innobase::prepare_inplace_alter_table() to ha_innobase::check_if_supported_inplace_alter(), but the API does not really allow us to return errors; it can only inform which forms of ALGORITHM and LOCK are allowed. So, we have to duplicate some logic between the "check" and "prepare" phases. We do the duplication by calling common functions. instant_alter_column_possible(): Check if instant column operation is possible. Invoked from both ha_innobase::check_if_supported_inplace_alter() and prepare_inplace_alter_table_dict(). ha_innobase::check_if_supported_inplace_alter(): Before refusing certain operations if FULLTEXT INDEX exist, check if instant ALTER TABLE is possible and return early if it is the case. prepare_inplace_alter_table_dict(): Before checking the limitations on FULLTEXT INDEX, check if instant ALTER TABLE is possible, and suppress the checks if it is the case. If instant ADD COLUMN is used when the table already contains FULLTEXT INDEX, do account for a hidden FTS_DOC_ID_INDEX in a debug assertion.
-
Marko Mäkelä authored
-
Marko Mäkelä authored
-
Marko Mäkelä authored
-
Marko Mäkelä authored
-
Daniel Black authored
finish_resize_simple_key_cache removed argument acquire for acquiring locks. resize_simple_key_cache enforces assertion that the cache is inited. read_block was really two functions, primary and secondary so separated as such. Make the callers of read_block explictly use the required function. Signed-off-by: Daniel Black <daniel@linux.vnet.ibm.com>
-
Monty authored
- Also added missing copyright notices
-
Igor Babaev authored
-
Igor Babaev authored
As a result of this merge the code for the following tasks appears in 10.3: - MDEV-12172 Implement tables specified by table value constructors - MDEV-12176 Transform [NOT] IN predicate with long list of values INTO [NOT] IN subquery.
-
- 01 Nov, 2017 22 commits
-
-
Varun Gupta authored
-
Varun Gupta authored
-
Varun Gupta authored
-
Varun Gupta authored
-
Varun Gupta authored
-
Varun Gupta authored
-
Varun Gupta authored
Added the median function to the parser , it should behave as a percentile_cont function with its argument fixed to 0.5
-
Varun Gupta authored
Added fix_fields for percentile function to check the type of argument and to ensure that only numeric arguments are allowed
-
Varun Gupta authored
-
Vicențiu Ciorbaru authored
Additionally, allow a query with window functions to be killed by the user during its execution.
-
Varun Gupta authored
Fixed indentation in the syntax rules for the sql_yacc.yy , also added the rules of the percentile functions to the sql_yacc_ora.yy
-
Varun Gupta authored
made changes according to the review, mostly removing unused code and fixing code to follow the coding conventions
-
Varun Gupta authored
-
Varun Gupta authored
1)ER_ARGUMENT_OUT_OF_RANGE: This error is thrown if the argument of the percentile function is not in the range [0,1] 2)ER_ARGUMENT_NOT_CONSTANT: This error is thrown if the argument of the percnetile function is not constant in the entire partition of the window function
-
Varun Gupta authored
Added the error ER_WRONG_TYPE_FOR_PERCENTILE_CONT, which ensures that the result type for percentile_cont is always numerical
-
Varun Gupta authored
Added the error ER_NOT_SINGLE_ELEMENT_ORDER_LIST for th percentile functions, these ensure that for the percentile function we have the order list with exactly one element
-
Varun Gupta authored
Added the function setting_handler_for_percentile_function() for the percentile_disc function that would set the type of the result field for percentile_disc. Percentile_cont would habe double precision result type
-
Varun Gupta authored
if we get any error during the add function call. This is currently used only for the percentile functions
-
Varun Gupta authored
-ER_NOT_SINGLE_ELEMENT_ORDER_LIST -ER_WRONG_TYPE_FOR_PERCENTILE_CONT -ER_ARGUMENT_NOT_CONSTANT -ER_ARGUMENT_OUT_OF_RANGE
-
Varun Gupta authored
Val_str function added for the percentile_disc function, as it can have result type as STRING_RESULT
-
Varun Gupta authored
Ensured that the the element in the order by clause should have a numerical time, if not throw an error
-
Varun Gupta authored
Percentile class implemented, most of the functions have the same functionalite as the percentile cont class
-