summaryrefslogtreecommitdiff
path: root/mysql-test/std_data
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch '10.0' into 10.1Sergei Golubchik2016-08-251-0/+1
|\
| * Merge branch '5.5' into 10.0Sergei Golubchik2016-08-101-0/+1
| |\
| | * Merge branch 'mysql/5.5' into 5.5Sergei Golubchik2016-08-031-0/+1
| | |\ | | | | | | | | | | | | without a fix for Bug#12818255 (MDEV-6581)
| | | * BUG#23080148 - BACKPORT BUG 14653594 AND BUG 20683959 TOThayumanavar S2016-06-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MYSQL-5.5 The bug asks for a backport of bug#1463594 and bug#20682959. This is required because of the fact that if replication is enabled, master transaction can commit whereas slave can't commit due to not exact 'enviroment'. This manifestation is seen in bug#22024200.
* | | | MDEV-8686 A user defined collation utf8_confusables doesn't workAlexander Barkov2016-06-231-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The collation customization code for the UCA (Unicode Collation Alrorithm) based collations now allows to reset to and shift of characters with implicit weights. Previously reset/shift worked only for the characters with explicit DUCET weights. An attempt to use reset/shift with character with implicit weights made the server crash.
* | | | MDEV-9383: Server fails to read master.info after upgrade 10.0 -> 10.1Kristian Nielsen2016-04-086-0/+213
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In some cases, MariaDB 10.0 could write a master.info file that was read incorrectly by 10.1 and could cause server to fail to start after an upgrade. (If writing a new master.info file that is shorter than the old, extra junk may remain at the end of the file. This is handled properly in 10.1 with an END_MARKER line, but this line is not written by 10.0. The fix here is to make 10.1 robust at reading the master.info files written by 10.0). Fix several things around reading master.info and read_mi_key_from_file(): - read_mi_key_from_file() did not distinguish between a line with and without an eqals '=' sign. - If a line was empty, read_mi_key_from_file() would incorrectly return the key from the previous call. - An extra using_gtid=X line left-over by MariaDB 10.0 might incorrectly be read and overwrite the correct value. - Fix incorrect usage of strncmp() which should be strcmp(). - Add test cases.
* | | | Add an empty file to std_data for future testing purposesVicențiu Ciorbaru2016-03-221-0/+0
| | | |
* | | | Merge branch '10.0' into 10.1Sergei Golubchik2016-02-235-0/+112
|\ \ \ \ | |/ / /
| * | | Merge branch '5.5' into 10.0Sergei Golubchik2016-02-155-0/+112
| |\ \ \ | | |/ /
| | * | Merge branch 'mysql/5.5' into 5.5Sergei Golubchik2016-02-095-0/+112
| | |\ \ | | | |/ | | | | | | | | | | | | reverted about half of commits as either not applicable or outright wrong
| | | * Bug #22295186: CERTIFICATE VALIDATION BUG IN MYSQL MAY ALLOW MITMYashwant Sahu2016-01-115-0/+112
| | | |
* | | | Merge branch 'github/10.0-galera' into 10.1Sergei Golubchik2015-11-195-0/+94
|\ \ \ \
| * \ \ \ Merge tag 'mariadb-10.0.22' into 10.0-galeraNirbhay Choubey2015-10-312-0/+71
| |\ \ \ \ | | |/ / /
| * | | | Galera MTR Tests: Instruct xtrabackup SST's socat to use 1024-bit DH keys to ↵Philip Stoev2015-09-091-0/+6
| | | | | | | | | | | | | | | | | | | | avoid 'error:14082174:SSL routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small'
| * | | | Galera MTR Tests: Tests for GRA*.log files, replication bundle, preordered ↵Philip Stoev2015-09-091-0/+0
| | | | | | | | | | | | | | | | | | | | events, forced binlog format
| * | | | Galera MTR Tests: various tests and test fixesPhilip Stoev2015-09-093-0/+88
| | | | |
| * | | | Merge tag 'mariadb-10.0.20' into 10.0-galeraNirbhay Choubey2015-06-213-0/+1
| |\ \ \ \
| * \ \ \ \ Merge tag 'mariadb-10.0.19' into 10.0-galeraNirbhay Choubey2015-05-0915-525/+496
| |\ \ \ \ \
| * | | | | | Merge galera tests from github.com/codership/mysql-wsrepNirbhay Choubey2015-05-083-0/+147
| | | | | | |
* | | | | | | MDEV-9011: Redo log encryption does not workJan Lindström2015-10-301-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Redo log encryption used too short buffer when getting encryption keys.
* | | | | | | Merge branch '10.0' into 10.1Sergei Golubchik2015-10-122-0/+71
|\ \ \ \ \ \ \ | | |_|_|/ / / | |/| | | | |
| * | | | | | Merge branch '5.5' into 10.0Sergei Golubchik2015-10-092-0/+71
| |\ \ \ \ \ \ | | |_|_|/ / / | |/| | | / / | | | |_|/ / | | |/| | |
| | * | | | Merge remote-tracking branch 'mysql/5.5' into 5.5Sergei Golubchik2015-10-082-0/+71
| | |\ \ \ \ | | | | |_|/ | | | |/| |
| | | * | | Bug #16171518 - LOAD XML DOES NOT HANDLE EMPTY ELEMENTSShishir Jaiswal2015-08-182-0/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | DESCRIPTION =========== Inability of mysql LOAD XML command to handle empty XML tags i.e. <row><tag/></row>. Also the behaviour is wrong and (different than above) when there is a space in empty tag i.e. <row><tag /></row> ANALYSIS ======== In read_xml() the case where we encounter a close tag ('/') we're decreasing the 'level' blindly which is wrong. Actually when its an without-space-empty-tag (succeeding char is '>'), we need to skip the decrement. In other words whenever we hit a close tag ('/'), decrease the 'level' only when (i) It's not an (without space) empty tag i.e. <tag/> or, (ii) It is of format <row col="val" .../> FIX === The switch case for '/' is modified. We've removed the blind decrement of 'level'. We do it only when its not an without-space-empty-tag. Also we are setting 'in_tag' to false to let program know that we're done reading current tag (required in the case of format <row col="val" .../>)
* | | | | | Merge branch '10.0-galera' into 10.1Nirbhay Choubey2015-07-143-0/+147
| | | | | |
* | | | | | Merge tag 'mariadb-10.0.20' into 10.1Sergei Golubchik2015-06-273-0/+1
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge branch '5.5' into 10.0Sergei Golubchik2015-06-113-0/+1
| |\ \ \ \ \ | | |/ / / / | | | | | / | | |_|_|/ | |/| | |
| | * | | MDEV-7269 mysqlbinlog Don't know how to handle column type=0 meta=0 (0000)#Alexander Barkov2015-06-043-0/+1
| | | | | | | | | | | | | | | | | | | | MDEV-8267 Add /*old*/ comment into I_S.COLUMN_TYPE for old DECIMAL
* | | | | Merge tag 'mariadb-10.0.19' into 10.1Sergei Golubchik2015-06-0115-525/+496
|\ \ \ \ \ | |/ / / /
| * | | | Merge branch '5.5' into 10.0Sergei Golubchik2015-05-0415-525/+496
| |\ \ \ \ | | |/ / / | | | | / | | |_|/ | |/| |
| | * | Merge branch 'openquery/MDEV-6916-maria-5.5-check_view-r4408' into 5.5Sergei Golubchik2015-04-288-0/+76
| | |\ \
| | | * | Update tests for mysql_upgrade_viewDaniel Black2015-04-141-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add bad checksum test Validate REPAIR VIEW {table} add mariadb-version to the frm Add tests for the binary logging of REPAIR VIEW
| | | * | Add mysql-test/std_data/mysql_upgrade/* for MDEV-6916Oleksandr Byelkin2015-04-137-0/+61
| | | | |
| | * | | MDEV-7859 SSL hostname verification fails for long subject namesSergei Golubchik2015-04-277-525/+420
| | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Don't use a fixed buffer for X509_NAME_oneline() in the client. Do as the server does - allocate it dynamically. For a test - regenerate certificates to have the server cert with a long subject.
* | | | MDEV-8238: Tables with encryption=yes using file_key_management plugin are ↵Jan Lindström2015-05-272-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | not encrypted Analysis: Problem was that encryption was skipped. Fixed by making sure that tables with ENCRYPTED=YES are encrypted.
* | | | tests for file_key_management plugin key file parserSergei Golubchik2015-04-081-3/+9
| | | |
* | | | completely rewrote file_key_management pluginSergei Golubchik2015-04-081-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | numerous issues fixed: * buffer overflows * error conditions aren't checked (crash if file doesn't exist) * accessing random unallocated memory * hard-coded password * arbitrary hard-coded key id limit * incomprehensible error messages (for key_id == 0 it reported "The key could not be initialized", for syntax errors the message was "Wrong match of the keyID, see the template", for a key id larger than hard-coded limit the message was "No asked key", and there was an error "Is comment" for a comment). * tons of small mallocs, many are freed few lines down in the code * malloc(N) and new char[N] are used both, even in the same function * redundant memory copies * pcre - "I can solve it with regular expressions" - with incorrect regexes * parser context stored in a singleton * keys are stored as strings and are strlen-ed and hex2bin-ed on every get_key() request * lots of useless code (e.g. sprintf instead of a pointer assignment, checking of the file length to read a part of it in a fixed buffer, multiplying by sizeof(char) in many places, etc) * this list is not exhaustive
* | | | Merge branch '10.0' into 10.1Sergei Golubchik2015-03-077-411/+525
|\ \ \ \ | |/ / /
| * | | Merge branch '5.5' into 10.0Sergei Golubchik2015-02-187-411/+525
| |\ \ \ | | |/ /
| | * | Merge remote-tracking branch 'mysql/5.5' into bb-5.5-merge @ mysql-5.5.42Sergei Golubchik2015-02-117-411/+525
| | |\ \ | | | |/
| | | * Bug#18366947 : VALID DATE RANGE OF DUMMY SSL CERTS IS WAY TOO SHORTHarin Vadodaria2014-12-057-250/+575
| | | | | | | | | | | | | | | | Generated new certificates with validity upto 2029.
| | | * Bug#16395459 TEST AND RESULT FILES WITH EXECUTE BITTerje Rosten2014-06-271-0/+0
| | | | | | | | | | | | | | | | Post push fix: add execute bit on perl script.
| | | * Bug#11747416 : 32228 A disk full makes binary log corruptAndrei Elkin2011-09-291-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Binary log of master can get a partially logged event if the server runs out of disk space and, while waiting for some space to be freed, is shut down (or crashes). If the server is not stopped, it will just wait endlessly for space to be freed, thus no partial event anomaly occurs. The restarted master server has had a dubious policy to send the incomplete event to slave which it apparently can't handle. Although an error was printed out the fact of sending with unclear error message is a source of confusion. Actually the problem of presence an incomplete event in the binary log was already fixed by WL 5493 (which was merged to our current trunk branch, major version 5.6). The fix makes the server truncate the binary log on server restart and recovery. However 5.5 master can't do that. So the current issue is a problem of sending incomplete events to the slave by 5.5 master. It is fixed in this patch by changing the policy so that only complete events are pushed by the dump thread to the IO thread. In addition, the error text that master sends to the slave when an incomplete event is found, now states that incomplete event may have been caused by an out-of-disk space situation and provides coordinates of the first and the last event bytes read.
| | | * Bug #11766328 59417: TEST BUGS.BUG57108 IS BROKEN:.....Bjorn Munch2011-07-221-95/+0
| | | | | | | | | | | | | | | | | | | | | | | | The test has been removed, no other tests are using this file (If any did, they would fail) Removing the file.
| | | * Updated/added copyright headersKent Boortz2011-06-301-2/+3
| | | |\
| | | | * Updated/added copyright headersKent Boortz2011-06-301-2/+3
| | | | |\
| | | * | \ MergeMagnus Blåudd2011-03-253-0/+0
| | | |\ \ \
| | | | * | | Bug#60111 storage type for table not saved in .frmMagnus Blåudd2011-03-043-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Add new "format section" in extra data segment with additional table and column properties. This was originally introduced in 5.1.20 based MySQL Cluster - Remove hardcoded STORAGE DISK for table and instead output the real storage format used. Keep both TABLESPACE and STORAGE inside same version guard. - Implement default version of handler::get_tablespace_name() since tablespace is now available in share and it's unnecessary for each handler to implement. (the function could actually be removed totally now). - Add test for combinations of TABLESPACE and STORAGE with CREATE TABLE and ALTER TABLE - Add test to show that 5.5 now can read a .frm file created by MySQL Cluster 7.0.22. Although it does not yet show the column level attributes, they are read.
| | | * | | | Bug #11755431 (former 47205)Jon Olav Hauglid2011-03-081-0/+0
| | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MAP 'REPAIR TABLE' TO RECREATE +ANALYZE FOR ENGINES NOT SUPPORTING NATIVE REPAIR Executing 'mysqlcheck --check-upgrade --auto-repair ...' will first issue 'CHECK TABLE FOR UPGRADE' for all tables in the database in order to check if the tables are compatible with the current version of MySQL. Any tables that are found incompatible are then upgraded using 'REPAIR TABLE'. The problem was that some engines (e.g. InnoDB) do not support 'REPAIR TABLE'. This caused any such tables to be left incompatible. As a result such tables were not properly fixed by the mysql_upgrade tool. This patch fixes the problem by first changing 'CHECK TABLE FOR UPGRADE' to return a different error message if the engine does not support REPAIR. Instead of "Table upgrade required. Please do "REPAIR TABLE ..." it will report "Table rebuild required. Please do "ALTER TABLE ... FORCE ..." Second, the patch changes mysqlcheck to do 'ALTER TABLE ... FORCE' instead of 'REPAIR TABLE' in these cases. This patch also fixes 'ALTER TABLE ... FORCE' to actually rebuild the table. This change should be reflected in the documentation. Before this patch, 'ALTER TABLE ... FORCE' was unused (See Bug#11746162) Test case added to mysqlcheck.test
| | | * | | Merge fix for bug 56817 from mysql-5.1 to mysql-5.5.John H. Embretsen2011-01-291-0/+97
| | | |\ \ \ | | | | |/ /
View Lorry Controller Status