An error occurred fetching the project authors.
- 16 Dec, 2016 3 commits
-
-
Alexander Barkov authored
Also fixes: MDEV-11331 Wrong result for INSERT INTO t1 (datetime_field) VALUES (hybrid_function_of_TIME_data_type) MDEV-11333 Expect "Impossible where condition" for WHERE timestamp_field>=DATE_ADD(TIMESTAMP'9999-01-01 00:00:00',INTERVAL 1000 YEAR) This patch does the following: 1. Splits the function Item::save_in_field() into pieces: - Item::save_str_in_field() - Item::save_real_in_field() - Item::save_decimal_in_field() - Item::save_int_in_field() 2. Adds the missing "no_conversion" parameters to Item::save_time_in_field() and Item::save_date_in_field(), so this parameter is now correctly passed to set_field_to_null_with_conversions(). This fixes the problem reported in 11333. 3. Introduces a new virtual method Type_handler::Item_save_in_field() and uses the methods Item::save_xxx_in_field() from the implementations of Type_handler_xxx::Item_save_in_field(). These changes additionally fix the problem reported in MDEV-11331, as the old code erroneously handled expressions like COALESE(datetime-expression) through the STRING_RESULT branch of Item::save_in_field() and therefore they looked like string type expressions for the target fields. Now such expressions are correctly handled by Item::save_date_in_field().
-
Alexander Barkov authored
MDEV-11294 Move definitions of Derivation, DTCollation, Type_std_attributes from field.h and item.h to sql_type.h
-
Alexander Barkov authored
-
- 14 Dec, 2016 1 commit
-
-
Igor Babaev authored
The patch for bug mdev-10882 tried to fix it by providing an implementation of the virtual method build_clone for the class Item_cache. It's turned out that it is not easy provide a valid implementation for Item_cache::build_clone(). At the same time if the condition that can be pushed into a materialized view contains a cached item this item can be substituted for a basic constant of the same value. In such a way we can avoid building proper clones for Item_cache objects when constructing pushdown conditions.
-
- 12 Dec, 2016 9 commits
-
-
Sergei Golubchik authored
by introducing new Item::precedence() method and using it to decide whether parentheses are required
-
Sergei Golubchik authored
-
Sergei Golubchik authored
now, when expr_str is gone, expr_item can be unambiguously renamed to expr.
-
Sergei Golubchik authored
otherwise we'd need to store sql_mode *per vcol* (consider CREATE INDEX...) and how SHOW CREATE TABLE would support that? Additionally, get rid of vcol::expr_str, just to make sure the string is always generated and never leaked in the original form.
-
Sergei Golubchik authored
-
Sergei Golubchik authored
update tests and results, fix bugs
-
Sergei Golubchik authored
will be used later by storage engines (e.g. in MyISAM repair or in InnoDB purge)
-
Sergei Golubchik authored
-
Sergei Golubchik authored
and partition_info::set_show_version_string - they were already broken and impossible to maintain
-
- 29 Nov, 2016 2 commits
-
-
Igor Babaev authored
The implementation of the virtual method build_clone for the class Item_cache was missing.
-
Oleksandr Byelkin authored
-
- 27 Nov, 2016 2 commits
-
-
Alexander Barkov authored
This patch adds DEFAULT as a possible dynamic SQL parameter, e.g.: EXECUTE IMMEDIATE 'INSERT INTO t1 (column) VALUES(?)' USING DEFAULT; EXECUTE IMMEDIATE 'UPDATE t1 SET column=?' USING DEFAULT; and for similar PREPARE..EXECUTE queries. This is done for symmetry with the STMT_INDICATOR_DEFAULT indicator in the client-server PS protocol. The changes include: - Allowing DEFAULT as a possible option in execute USING clause (sql_yacc.yy) - Adding "virtual bool Item::save_in_param(THD *thd, Item_param *param)", because "normal" items (that have real values) and Item_default_value have now different actions when assigning itself as an Item_param value. - Fixing switch() statements in a few Item_param methods not to have "default", because it was easy to forget to add a new "case" when adding a new XXX_VALUE value into the enum Item_param::enum_item_param_state. This is important, as we'll be adding new values soon, e.g. for MDEV-11359. Removing "default" helped to find and report bugs MDEV-11361 and MDEV-11362, because DECIMAL_VALUE is obviously not properly handled in some cases.
-
Igor Babaev authored
The fix for bug 11072 was not complete though it also fixed the bug mdev-10800. This patch resolves the problems of all three bugs.
-
- 23 Nov, 2016 1 commit
-
-
Igor Babaev authored
There were no implementations for the virtual functions exclusive_dependence_on_table_processor and exclusive_dependence_on_table_processor. As a result the procedure pushdown_cond_for_derived erroneously detected some conditions with outer references as pushable into materialized view / derived table.
-
- 15 Nov, 2016 2 commits
-
-
Igor Babaev authored
In a general case the conditions with outer fields cannot be pushed into materialized views / derived tables. However if the outer field in the condition refers to a single row table then the condition may be pushable. In this case a special care should be taken for outer fields when pushing the condition into a materialized view / derived table.
-
Alexey Botchkov authored
The rest of mysql/json functions implemented. CAST AS JSON implemented.
-
- 02 Nov, 2016 1 commit
-
-
Oleksandr Byelkin authored
(+ default values)
-
- 25 Oct, 2016 1 commit
-
-
Alexey Botchkov authored
Item_bool fixed to behave smarter with NOT operation.
-
- 19 Oct, 2016 1 commit
-
-
Alexey Botchkov authored
strings/json_lib.c added as a JSON library. SQL frunction added with sql/item_jsonfunc.h/cc
-
- 08 Oct, 2016 2 commits
-
-
Alexander Barkov authored
-
Alexander Barkov authored
-
- 05 Sep, 2016 1 commit
-
-
Igor Babaev authored
for materialized views and derived tables: there were no push-down if the view was defined as union of selects without aggregation. Added test cases with such unions. Adjusted result files after the merge of the code for mdev-9197.
-
- 02 Sep, 2016 1 commit
-
-
Igor Babaev authored
Adjusted one result file.
-
- 27 Aug, 2016 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
as in create table t1 (a int); create view v1 as select default(a) as NOT_UPDATABLE from t1;
-
- 22 Aug, 2016 1 commit
-
-
Galina Shalygina authored
-
- 03 Jul, 2016 3 commits
-
-
Alexander Barkov authored
Adding Converter_double_to_longlong and reusing it in: 1. Field_longlong::store(double nr) 2. Field_double::val_int() 3. Item::val_int_from_real() 4. Item_dyncol_get::val_int() As a good side efferct, now overflow in conversion in the mentioned val_xxx() methods return exactly the same warning.
-
Alexander Barkov authored
(MDEV-9407, MDEV-9408) from 10.1 Needed to fix MDEV-10317 easier.
-
Alexander Barkov authored
"thd" is available through the "table" argument, as table->in_use. Backporting (partially) from 10.2.
-
- 01 Jul, 2016 2 commits
-
-
Sergei Golubchik authored
because table->map is set much later. Use check_vcol_func_processor() to detect fields too.
-
Alexander Barkov authored
"thd" is available through the "table" argument, as table->in_use.
-
- 30 Jun, 2016 5 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
and remove all related casts to uchar* also remove a couple of unused methods
-
Sergei Golubchik authored
-
Michael Widenius authored
- Force usage of () around complex DEFAULT expressions - Give error if DEFAULT expression contains invalid characters - Don't use const_charset_conversion for stored Item_func_sysconf expressions as the result is not constaint over different executions - Fixed Item_func_user() to not store calculated value in str_value
-