summaryrefslogtreecommitdiff
path: root/mysql-test/suite/sql_sequence
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch '10.9' into 10.10Oleksandr Byelkin2022-11-012-0/+182
|\
| * Merge branch '10.6' into 10.7Oleksandr Byelkin2022-10-292-0/+182
| |\
| | * Merge 10.5 into 10.6Marko Mäkelä2022-10-252-0/+182
| | |\ | | | | | | | | | | | | | | | | | | | | To prevent ASAN heap-use-after-poison in the MDEV-16549 part of ./mtr --repeat=6 main.derived the initialization of Name_resolution_context was cleaned up.
| | | * Merge 10.4 into 10.5Marko Mäkelä2022-10-252-0/+182
| | | |\
| | | | * Merge 10.3 into 10.4Marko Mäkelä2022-10-252-0/+182
| | | | |\
| | | | | * MDEV-29540 Incorrect sequence values in INSERT SELECTDaniel Black2022-10-192-0/+182
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The population of default values in INSERT SELECT was being performed twice. With sequences, this resulted in every second sequence value being used. With SELECT INSERT we remove the second invokation of table->update_default_fields(). This was already performed in store_values() invoking fill_record_n_invoke_before_triggers() which invoked update_default_fields() previously. We do need to return an error on duplicate values, so the ::store_values is extended to take the ignore option.
* | | | | | Merge branch '10.9' into 10.10Oleksandr Byelkin2022-10-044-16/+16
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge branch '10.6' into 10.7Oleksandr Byelkin2022-10-044-16/+16
| |\ \ \ \ \ | | |/ / / /
| | * | | | Merge branch '10.5' into 10.6Sergei Golubchik2022-10-024-16/+16
| | |\ \ \ \ | | | |/ / /
| | | * | | Merge branch '10.4' into 10.5Sergei Golubchik2022-10-024-16/+16
| | | |\ \ \ | | | | |/ /
| | | | * | Merge branch '10.3' into 10.4Sergei Golubchik2022-10-014-16/+16
| | | | |\ \ | | | | | |/
| | | | | * MDEV-28548: ER_TABLEACCESS_DENIED_ERROR is missing information about DBAnel Husakovic2022-09-304-16/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Added missing information about database of corresponding table for various types of commands - Update some typos - Reviewed by: <vicentiu@mariadb.org>
* | | | | | Merge 10.9 into 10.10Marko Mäkelä2022-09-213-10/+10
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge 10.6 into 10.7Marko Mäkelä2022-09-213-10/+10
| |\ \ \ \ \ | | |/ / / /
| | * | | | Merge 10.5 into 10.6Marko Mäkelä2022-09-203-10/+10
| | |\ \ \ \ | | | |/ / /
| | | * | | Merge remote-tracking branch 'origin/10.4' into 10.5Alexander Barkov2022-09-143-10/+10
| | | |\ \ \ | | | | |/ /
| | | | * | Merge 10.3 into 10.4Marko Mäkelä2022-09-133-10/+10
| | | | |\ \ | | | | | |/
| | | | | * MDEV-29446 Change SHOW CREATE TABLE to display default collationAlexander Barkov2022-09-123-10/+10
| | | | | |
| | | * | | MDEV-13005 after-merge fixupMarko Mäkelä2022-04-062-2/+2
| | | | | |
* | | | | | cleanup: testsSergei Golubchik2022-08-104-4/+4
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | sequence tests verify that one cannot change the structure of the table. for that they need a valid alter table that adds an index over an existing column. there's no column 'start' in the table
* | | | | Merge 10.6 into 10.7Marko Mäkelä2022-04-0610-32/+100
|\ \ \ \ \ | |/ / / /
| * | | | Merge 10.5 into 10.6Marko Mäkelä2022-04-0610-32/+100
| |\ \ \ \ | | |/ / /
| | * | | Merge 10.4 into 10.5Marko Mäkelä2022-04-0610-32/+100
| | |\ \ \ | |/ / / / | | | _ / | | | /
| | * | MDEV-13005: Fixing bugs in SEQUENCE, part 3, 5/5Rucha Deodhar2022-03-302-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Task 6: We can find the .frm type of file. If it is sequence then is_sequence passed to dd_frm_type() will be true. Since there is already a check to give error message if we trigger is on temporary table or view, an additional condition is added to check if .frm is sequence (is_sequence==true) and error message is changed to show "Trigger's '%-.192s' is view, temporary table or sequence" instead of "Trigger's '%-.192s' is view or temporary table".
| | * | MDEV-13005: Fixing bugs in SEQUENCE, part 3, 4/5Rucha Deodhar2022-03-302-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Task 4 and 5: Already fixed when I started working on bug. Task 4 correctly gives syntax error ('(' and ')' are not part of create sequence syntax). Task 5 also gives correct error because s1 is table not sequence. Fails with ER_NOT_SEQUENCE2
| | * | MDEV-13005: Fixing bugs in SEQUENCE, part 3, 3/5Rucha Deodhar2022-03-302-0/+7
| | | | | | | | | | | | | | | | | | | | Task 3: Added an additional condition for SEQUENCE option to check if cache < 0.
| | * | MDEV-13005: Fixing bugs in SEQUENCE, part 3, 2/5Rucha Deodhar2022-03-307-22/+29
| | | | | | | | | | | | | | | | | | | | Task 2: changed the error message and made it more reusable.
| | * | MDEV-13005: Fixing bugs in SEQUENCE, part 3, 1/5Rucha Deodhar2022-03-306-10/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Task 1: If table is added to list using option TL_OPTION_SEQUENCE (done when we have sequence functions) then then we are dealing with sequence instead of table. So global table list will have sequence set to true. This is used to check and give correct error message about unknown sequence instead of table doesn't exist.
* | | | Merge 10.6 into 10.7Marko Mäkelä2022-03-112-2/+38
|\ \ \ \ | |/ / /
| * | | Merge 10.4 into 10.5Marko Mäkelä2022-03-112-2/+38
| |\ \ \ | | |/ /
| | * | Merge 10.3 into 10.4Marko Mäkelä2022-03-112-2/+38
| | |\ \ | | | |/
| | | * MDEV-24617 OPTIMIZE on a sequence causes unexpected ER_BINLOG_UNSAFE_STATEMENTAndrei2022-03-102-2/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The warning out of OPTIMIZE Statement is unsafe because it uses a system function was indeed counterfactual and was resulted by checking an insufficiently strict property of lex' sql_command_flags. Fixed with deploying an additional checking of weather the current sql command that modifes a share->non_determinstic_insert table is capable of generating ROW format events. The extra check rules out the unsafety to OPTIMIZE et al, while the existing check continues to do so to CREATE TABLE (which is perculiarly tagged as ROW-event generative sql command). As a side effect sql_sequence.binlog test gets corrected and binlog_stm_unsafe_warning.test is reinforced to add up an unsafe CREATE..SELECT test.
* | | | MDEV-25152: Insert linebreaks in mysqldump --extended-insertDaniel Black2021-10-011-4/+12
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Per review by Serg, include start row with new line. We are hoping we haven't annoyed people that prefered the old way. Adding an option for new lines seems like over-engineering in advance. So if there are complaints, let them be known (JIRA), and we'll add this under an option. Test cases updated.
* | | Merge 10.4 into 10.5Marko Mäkelä2021-08-312-0/+22
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2021-08-312-0/+22
| |\ \ | | |/
| | * MDEV 22785 Crash with prepared statements and NEXTVAL()Michael Widenius2021-08-262-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | The problem was that a PREARE followed by a non prepared statement using DEFAULT NEXT_VALUE() could change table->next_local to point to a not persitent memory aria. The next EXECUTE would then try to use the wrong pointer, which could cause a crash. Fixed by reseting the pointer to it's old value when doing EXECUTE.
| * | Merge branch 10.3 into 10.4Daniel Black2021-07-021-0/+2
| |\ \ | | |/
| | * mtr: fix tests funcs_1.is_tables_is & sql_sequence.rebuildDaniel Black2021-07-021-0/+2
| | |
* | | Merge 10.4 into 10.5Marko Mäkelä2021-04-272-0/+32
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2021-04-272-0/+32
| |\ \ | | |/
| | * MDEV-24545 Sequence created by one connection remains invisible to anotherst-10.3Marko Mäkelä2021-04-272-0/+32
| | | | | | | | | | | | | | | | | | row_merge_is_index_usable(): Allow access to any SEQUENCE, even if it was created after the read view. SQL sequences are no-rollback tables with no history at all.
* | | Merge branch 'bb-10.4-release' into bb-10.5-releaseSergei Golubchik2021-02-152-0/+53
|\ \ \ | |/ /
| * | Merge branch 'bb-10.3-release' into bb-10.4-releaseSergei Golubchik2021-02-122-0/+53
| |\ \ | | |/ | | | | | | | | | 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
| | * MDEV-21785: sequences used as default by other table not dumped in right ↵bb-10.3-MDEV-21785Oleksandr Byelkin2021-01-262-0/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | order by mysqldump Dump sequences first. This atch made to keep it small and to keep number of queries to the server the same. Order of tables in a dump can not be changed (except sequences first) because mysql_list_tables uses SHOW TABLES and I used SHOW FULL TABLES.
* | | Merge commit '10.4' into 10.5Oleksandr Byelkin2021-01-062-0/+120
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2020-12-234-2/+125
| |\ \ | | |/
| | * MDEV-19273: Server crash in MDL_ticket::has_stronger_or_equal_type or ↵bb-10.3-MDEV-19273Oleksandr Byelkin2020-12-094-2/+125
| | | | | | | | | | | | | | | | | | | | | | | | Assertion `thd->mdl_context.is_lock_owner(MDL_key::TABLE, table->db.str, table->table_name.str, MDL_SHARED)' failed in mysql_rm_table_no_locks Early report error in case of DROP SEQUENCE <non-sequence> Do not use error variable for other purposes except error.
* | | Merge 10.4 into 10.5Marko Mäkelä2020-10-303-28/+16
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2020-10-293-28/+16
| |\ \ | | |/
| | * MDEV-24018: SIGSEGV in Item_func_nextval::update_table on SELECT SETVALAnel Husakovic2020-10-272-0/+12
| | | | | | | | | | | | Reviewed-by: wlad@mariadb.com
View Lorry Controller Status