summaryrefslogtreecommitdiff
path: root/mysql-test/main/myisam.result
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-22189: Change error messages inside code to have mariadb instead ofRucha Deodhar2021-05-241-1/+1
| | | | | | | mysql Fix: Changed error messages, rerecorded results and changed other relevant files.
* Add support for minimum field width for strings to my_vsnprintf()Monty2021-05-191-4/+4
| | | | | | | | This patch adds support for right aligned strings and numbers. Left alignment is left as an exercise for anyone needing it. MDEV-25612 "Assertion `to <= end' failed in process_args" fixed. (Was caused by the original version of this patch)
* MDEV-8334: Rename utf8 to utf8mb3Rucha Deodhar2021-05-191-3/+3
| | | | | | This patch changes the main name of 3 byte character set from utf8 to utf8mb3. New old_mode UTF8_IS_UTF8MB3 is added and set TRUE by default, so that utf8 would mean utf8mb3. If not set, utf8 would mean utf8mb4.
* MDEV-7317: Make an index ignorable to the optimizerVarun Gupta2021-03-041-63/+63
| | | | | | | | | | | | | | This feature adds the functionality of ignorability for indexes. Indexes are not ignored be default. To control index ignorability explicitly for a new index, use IGNORE or NOT IGNORE as part of the index definition for CREATE TABLE, CREATE INDEX, or ALTER TABLE. Primary keys (explicit or implicit) cannot be made ignorable. The table INFORMATION_SCHEMA.STATISTICS get a new column named IGNORED that would store whether an index needs to be ignored or not.
* Merge branch 'bb-10.4-release' into bb-10.5-releaseSergei Golubchik2021-02-151-7/+8
|\
| * Merge branch 'bb-10.3-release' into bb-10.4-releaseSergei Golubchik2021-02-121-7/+8
| |\ | | | | | | | | | | | | Note, the fix for "MDEV-23328 Server hang due to Galera lock conflict resolution" was null-merged. 10.4 version of the fix is coming up separately
| | * Merge branch '10.2' into 10.3Sergei Golubchik2021-02-011-7/+8
| | |
* | | MDEV-18650: Options deprecated in previous versions - storage_engineVicențiu Ciorbaru2020-02-131-2/+2
| | | | | | | | | | | | | | | | | | | | | Remove usage of deprecated variable storage_engine. It was deprecated in 5.5 but it never issued a deprecation warning. Make it issue a warning in 10.5.1. Replaced with default_storage_engine.
* | | MDEV-8844 Unreadable control characters printed as is in warningsAlexander Barkov2019-12-061-1/+1
|/ /
* | Merge remote-tracking branch 'origin/10.3' into 10.4Alexander Barkov2019-10-011-0/+23
|\ \ | |/
| * Merge remote-tracking branch 'origin/10.2' into 10.3Alexander Barkov2019-10-011-0/+23
| |
* | MDEV-13628: ORed condition in pushed index condition is not removed from the ↵Varun Gupta2019-05-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WHERE So to push index condition for each join tab we have calculate the index condition that can be pushed and then remove this index condition from the original condition. This is done through the function make_cond_remainder. The problem is the function make_cond_remainder does not remove index condition when there is an OR operator. Fixed this by making the function make_cond_remainder to keep in mind of the OR operator. Also updated results for multiple test files which were incorrectly updated by the commit e0c1b3f24246d22e6785315f9a8448bd9a590422 code which was supposed to remove the condition present in the index condition was not getting executed when the condition had OR operator, with AND the pushed index condition was getting removed from where. This problem affects all versions starting from 5.5 but this is a performance improvement, so fixing it in 10.4
* | Merge 10.3 into 10.4Marko Mäkelä2019-04-251-1/+7
|\ \ | |/ | | | | | | In is_eits_usable(), we disable an assertion that fails due to MDEV-19334.
* | Merge branch '10.4' into bb-10.4-mdev16188Igor Babaev2019-02-031-1/+7
|\ \
| * | MDEV-15253: Default optimizer setting changes for MariaDB 10.4Varun Gupta2018-12-091-1/+7
| | | | | | | | | | | | | | | use_stat_tables= PREFERABLY optimizer_use_condition_selectivity= 4
* | | MDEV-16188 Use in-memory PK filters built from range index scansIgor Babaev2019-02-031-2/+2
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch contains a full implementation of the optimization that allows to use in-memory rowid / primary filters built for range   conditions over indexes. In many cases usage of such filters reduce   the number of disk seeks spent for fetching table rows. In this implementation the choice of what possible filter to be applied   (if any) is made purely on cost-based considerations. This implementation re-achitectured the partial implementation of the feature pushed by Galina Shalygina in the commit 8d5a11122c32f4d9eb87536886c6e893377bdd07. Besides this patch contains a better implementation of the generic   handler function handler::multi_range_read_info_const() that takes into account gaps between ranges when calculating the cost of range index scans. It also contains some corrections of the implementation of the handler function records_in_range() for MyISAM. This patch supports the feature for InnoDB and MyISAM.
* | MDEV-17068 mysql system table is marked as crashed and should be repaired ↵Monty2018-08-281-1/+1
|/ | | | | | | | | | | after the server crashes or is killed - Changed ERROR to WARNING for MyISAM/Aria message that are warnings in the check utilities. This affects for example "client is using or hasn't closed the table properly". - Print "Table is fixed" if check succeded in fixing the table.
* Merge remote-tracking branch '10.2' into 10.3Vicențiu Ciorbaru2018-04-121-3/+4
|
* Create 'main' test directory and move 't' and 'r' thereMichael Widenius2018-03-291-0/+2671