summaryrefslogtreecommitdiff
path: root/mysql-test/suite/vcol/r
Commit message (Collapse)AuthorAgeFilesLines
...
* | | followup for MDEV-6996, update tests and resultsSergei Golubchik2014-12-036-8/+14
|/ /
* | 5.5 mergeSergei Golubchik2014-11-191-0/+67
|\ \ | |/
| * MDEV-7113 difference between check_vcol_func_processor and ↵Sergei Golubchik2014-11-181-0/+67
| | | | | | | | | | | | | | | | | | | | | | | | check_partition_func_processor MDEV-6789 segfault in Item_func_from_unixtime::get_date on updating table with virtual columns * prohibit VALUES in partitioning expression * prohibit user and system variables in virtual column expressions * fix Item_func_date_format to cache locale (for %M/%W to return the same as MONTHNAME/DAYNAME) * fix Item_func_from_unixtime to cache time_zone directly, not THD (and not to crash) * added tests for other incorrectly allowed (in vcols) functions to see that they don't crash
* | MDEV-6103 - Adding/removing non-materialized virtual column triggersSergey Vojtovich2014-06-032-0/+32
| | | | | | | | | | | | | | table recreation Relaxed InnoDB/XtraDB checks to allow online add/drop of non-materialized virtual columns.
* | 10.0-base mergeSergei Golubchik2014-02-261-0/+5
|\ \
| * \ 5.5 mergeSergei Golubchik2014-02-251-0/+5
| |\ \ | | |/
| | * Merge 5.3->5.5Igor Babaev2014-02-101-0/+5
| | |\
| | | * Fixed bug mdev-5611.Igor Babaev2014-02-071-0/+5
| | | | | | | | | | | | | | | | | | | | The method Item_field::update_table_bitmaps() should not try to mark the bit for a self-referencing virtual column.
| * | | MDEV-5244: Make extended_keys=ON by default in 10.0Sergey Petrunya2014-02-251-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | - Change the default flag value to ON. - Update the testcases to be run extended_keys=ON: = trivial test result updates = If extended_keys setting makes a difference for a testcase, run the testcase with extended_keys=off. There were only a few such cases - Update to vcol_select_innodb looks like a worse plan but it will be gone in 10.0.
* | | 5.5 merge and fixes for compiler/test errorsSergei Golubchik2013-09-181-0/+8
|\ \ \ | |/ /
| * | Merge 5.3->5.5.Igor Babaev2013-08-181-0/+8
| |\ \ | | |/ | | | | | | | | | | | | | | | In particular: Merged the patch for bug mdev-4418 from 5.3 into 5.5. Fixed a bug in the patch that should be backported to 5.3.
| | * Merge 5.2->5.3Igor Babaev2013-08-151-0/+8
| | |\
| | | * MDEV-4823: Server crashes in Item_func_not::fix_fields on creating a table ↵unknown2013-08-011-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | with a virtual column using NOT fix_field() call protocol was brocken (zero pointer passed as link to item which is possible only if you are sure that there can not be Items which transforms).
* | | | 5.5 mergeSergei Golubchik2013-07-171-0/+4
|\ \ \ \ | |/ / /
| * | | Merging from 5.3Alexander Barkov2013-07-081-0/+4
| |\ \ \ | | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | modified: include/my_time.h libmysql/libmysql.c mysql-test/r/adddate_454.result mysql-test/r/cast.result mysql-test/r/date_formats.result mysql-test/r/func_sapdb.result mysql-test/r/func_time.result mysql-test/r/mdev316.result mysql-test/r/parser.result mysql-test/r/partition_datatype.result mysql-test/r/partition_pruning.result mysql-test/r/type_date.result mysql-test/r/type_datetime.result mysql-test/suite/vcol/r/vcol_misc.result mysql-test/t/cast.test sql-common/my_time.c sql/field.cc sql/field_conv.cc sql/filesort.cc sql/item.cc sql/item.h sql/item_cmpfunc.cc sql/item_func.cc sql/item_strfunc.cc sql/item_timefunc.cc sql/sql_time.cc pending merges: Sergei Golubchik 2013-07-03 MDEV-4667 DATE('string') incompability betwe...
| | * | MDEV-4667 DATE('string') incompability between mysql and mariadbSergei Golubchik2013-07-031-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cleanup: remove TIME_FUZZY_DATE. Introduce TIME_FUZZY_DATES which means "very fuzzy, the resulting value is only used for comparison. It can be invalid date, fine, as long as it can be compared". Updated many tests results (they're better now).
* | | | 5.5 mergeSergei Golubchik2013-01-291-0/+11
|\ \ \ \ | |/ / /
| * | | Merge 5.3->5.5Igor Babaev2013-01-231-0/+11
| |\ \ \ | | |/ /
| | * | Merge 5.2->5.3Igor Babaev2013-01-211-0/+11
| | |\ \ | | | |/
| | | * Corrected the test case for bug mdev-3938.Igor Babaev2013-01-191-0/+1
| | | |
| | | * Fixed bug mdev-3938.Igor Babaev2013-01-151-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | The original patch with the implementation of virtual columns did not support INSERT DELAYED into tables with virtual columns. This patch fixes the problem.
* | | | simplify the handler api - table_type() is no longer abstract, not even virtualSergei Golubchik2012-12-171-1/+1
|/ / /
* | | 5.3->5.5 mergeSergei Golubchik2012-11-222-0/+80
|\ \ \ | |/ /
| * | Merge MariaDB 5.2->5.3unknown2012-11-202-0/+80
| |\ \ | | |/
| | * Fixed bug mdev-3845.Igor Babaev2012-11-092-0/+80
| | | | | | | | | | | | | | | | | | If triggers are used for an insert/update/delete statement than the values of all virtual columns must be computed as any of them may be used by the triggers.
* | | Merge 5.3->5.5.Igor Babaev2012-06-241-0/+36
|\ \ \ | |/ /
| * | Merge 5.2->5.3Igor Babaev2012-06-231-0/+36
| |\ \ | | |/
| | * Fixed bug mdev-354.Igor Babaev2012-06-181-0/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Virtual columns of ENUM and SET data types were not supported properly in the original patch that introduced virtual columns into MariaDB 5.2. The problem was that for any virtual column the patch used the interval_id field of the definition of the column in the frm file as a reference to the virtual column expression. The fix stores the optional interval_id of the virtual column in the extended header of the virtual column expression.
* | | Merge 5.3->5.5Igor Babaev2012-03-171-0/+13
|\ \ \ | |/ /
| * | Merge 5.2->5.3unknown2012-03-141-0/+13
| |\ \ | | |/
| | * Fixed LP bug #930814.Igor Babaev2012-03-091-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | This bug was introduced into mariadb 5.2 in the December 2010 with the patch that added a new engine property: the ability to support virtual columns. As a result of this bug the information from frm files for tables that contained virtual columns did not appear in the information schema tables.
* | | 5.3 mergeSergei Golubchik2012-02-211-3/+3
|\ \ \ | |/ /
| * | Backport of:Sergey Petrunya2012-02-161-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | timestamp: Thu 2011-12-01 15:12:10 +0100 Fix for Bug#13430436 PERFORMANCE DEGRADATION IN SYSBENCH ON INNODB DUE TO ICP When running sysbench on InnoDB there is a performance degradation due to index condition pushdown (ICP). Several of the queries in sysbench have a WHERE condition that the optimizer uses for executing these queries as range scans. The upper and lower limit of the range scan will ensure that the WHERE condition is fulfilled. Still, the WHERE condition is part of the queries' condition and if ICP is enabled the condition will be pushed down to InnoDB as an index condition. Due to the range scan's upper and lower limits ensure that the WHERE condition is fulfilled, the pushed index condition will not filter out any records. As a result the use of ICP for these queries results in a performance overhead for sysbench. This overhead comes from using resources for determining the part of the condition that can be pushed down to InnoDB and overhead in InnoDB for executing the pushed index condition. With the default configuration for sysbench the range scans will use the primary key. This is a clustered index in InnoDB. Using ICP on a clustered index provides the lowest performance benefit since the entire record is part of the clustered index and in InnoDB it has the highest relative overhead for executing the pushed index condition. The fix for removing the overhead ICP introduces when running sysbench is to disable use of ICP when the index used by the query is a clustered index. When WL#6061 is implemented this change should be re-evaluated.
* | | 5.3.4 mergeSergei Golubchik2012-02-153-4/+34
|\ \ \ | |/ /
| * | Merge 5.2->5.3 in preparation for the release of mariadb-5.3.4-rc.Igor Babaev2012-02-011-0/+30
| |\ \ | | |/
| | * Fixed LP bug #806057.Igor Babaev2011-12-291-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | A table expression with a natural join or a USING clause is transformed into an equivalent expression with equi-join ON conditions. If a reference to a virtual column happened to occur only in these generated equi-join conditions then it was not erroneously marked in the TABLE::vcol_set bitmap. This could lead to wrong results for queries containing natural join expressions or USING clauses.
| * | Fixed LP bug #917990.Igor Babaev2012-01-182-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the expression for a derived table of a query contained a LIMIT clause the estimate of the number of rows in this derived table returned by the EXPLAIN command could be badly off since the optimizer ignored the limit number from the LIMIT clause when getting the estimate. The call of the method SELECT_LEX_UNIT->set_limit added in the code of mysql_derived_optimize() will be needed also in maria-5.5 where parameters in the LIMIT clause are supported.
* | | 5.3 mergeSergei Golubchik2012-01-135-1/+13
|\ \ \ | |/ /
| * | Made the optimizer switch flags 'outer_join_with_cache', 'semijoin_with_cache'Igor Babaev2011-12-152-0/+6
| | | | | | | | | | | | set to 'on' by default.
| * | Merge with 5.2.Michael Widenius2011-12-112-11/+10
| |\ \ | | |/ | | | | | | no_error handling for select (used by INSERT ... SELECT) still needs to be fixed, but I will do that in a separate commit
| | * Merge with MariaDB 5.1Michael Widenius2011-11-242-10/+9
| | |
| * | Set new default values for the optimizer switch flags 'derived_merge'Igor Babaev2011-11-262-0/+6
| | | | | | | | | | | | and 'derived_with_keys'. Now they are set on by default.
* | | after merge changes:Sergei Golubchik2011-12-126-40/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * rename all debugging related command-line options and variables to start from "debug-", and made them all OFF by default. * replace "MySQL" with "MariaDB" in error messages * "Cast ... converted ... integer to it's ... complement" is now a note, not a warning * @@query_cache_strip_comments now has a session scope, not global.
* | | 5.3->5.5 mergeSergei Golubchik2011-11-272-19/+19
|\ \ \ | |/ /
| * | Made the optimizer switch for index condition pushdown set to 'on' by default. Igor Babaev2011-11-212-16/+16
| | |
| * | merging.Alexey Botchkov2011-11-123-20/+25
| |\ \
| * \ \ gis-related tests fixes.Alexey Botchkov2011-06-2013-50/+166
| |\ \ \ | | | | | | | | | | | | | | | | | | | | merging.
* | \ \ \ 5.3->5.5 mergeSergei Golubchik2011-11-223-8/+11
|\ \ \ \ \ | | |_|/ / | |/| | |
| * | | | Change the default @@optimizer_switch settings:Sergey Petrunya2011-11-022-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - More test result updates
| * | | | Fixed a cost estimation bug introduced into in the function best_access_pathIgor Babaev2011-09-301-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | of the 5.3 code line after a merge with 5.2 on 2010-10-28 in order not to allow the cost to access a joined table to be equal to 0 ever. Expanded data sets for many test cases to get the same execution plans as before.
View Lorry Controller Status