summaryrefslogtreecommitdiff
path: root/mysql-test/main/partition_error.result
Commit message (Collapse)AuthorAgeFilesLines
* Merge 10.7 into 10.8Marko Mäkelä2022-09-211-6/+6
|\
| * Merge 10.6 into 10.7Marko Mäkelä2022-09-211-6/+6
| |\
| | * Merge remote-tracking branch 'origin/10.4' into 10.5Alexander Barkov2022-09-141-6/+6
| | |\
| | | * MDEV-29446 Change SHOW CREATE TABLE to display default collationAlexander Barkov2022-09-121-6/+6
| | | |
* | | | Merge 10.7 into 10.8Marko Mäkelä2022-06-061-1/+12
|\ \ \ \ | |/ / /
| * | | Merge 10.6 into 10.7Marko Mäkelä2022-06-061-1/+12
| |\ \ \ | | |/ /
| | * | Merge 10.4 into 10.5Marko Mäkelä2022-06-021-1/+12
| | |\ \ | | | |/
| | | * MDEV-28599 EXCHANGE PARTITION on view causes ER_CHECK_NO_SUCH_TABLE instead ↵Masashi Tomooka2022-05-301-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | of ER_WRONG_OBJECT ER_CHECK_NO_SUCH_TABLE was raised because a view does not have the corresponding TABLE instance connected to TABLE_LIST and the server interprets the absence as the absence of the table itself. To fix the problem, we add a check to ensure that the target table to be swapped with a partition is not a view. Reviewed by: Nayuta Yanagisawa
* | | | MDEV-5271 Support engine-defined attributes per partitionNayuta Yanagisawa2022-01-241-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make it possible to specify engine-defined attributes on partitions as well as tables. If an engine-defined attribute is only specified at the table level, it applies to all the partitions in the table. This is a backward-compatible behavior. If the same attribute is specified both at the table level and the partition level, the per-partition one takes precedence. So, we can consider per-table attributes as default values. One cannot specify engine-defined attributes on subpartitions. Implementation details: * We store per-partition attributes in the partition_element class because we already have the part_comment field, which is for per-partition comments. * In the case of ALTER TABLE statements, the partition_elements in table->part_info is set up by mysql_unpack_partition(). So, we parse per-partition attributes after the call of the function.
* | | Vanilla cleanups and refactoringsAleksey Midenkov2021-10-261-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Dead code cleanup: part_info->num_parts usage was wrong and working incorrectly in mysql_drop_partitions() because num_parts is already updated in prep_alter_part_table(). We don't have to update part_info->partitions because part_info is destroyed at alter_partition_lock_handling(). Cleanups: - DBUG_EVALUATE_IF() macro replaced by shorter form DBUG_IF(); - Typo in ER_KEY_COLUMN_DOES_NOT_EXITS. Refactorings: - Splitted write_log_replace_delete_frm() into write_log_delete_frm() and write_log_replace_frm(); - partition_info via DDL_LOG_STATE; - set_part_info_exec_log_entry() removed. DBUG_EVALUATE removed DBUG_EVALUTATE was only added for consistency together with DBUG_EVALUATE_IF. It is not used anywhere in the code. DBUG_SUICIDE() fix on release build On release DBUG_SUICIDE() was statement. It was wrong as DBUG_SUICIDE() is used in expression context.
* | | MDEV-12914: Engine for temporary tables which are implicitly created as ↵Anel Husakovic2021-07-101-1/+1
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | RocksDB is substituted silently - There should be no substitution if engine exists, only when doesn't exist - Handling of an error when sys_var `default_tmp_storage_engine` is assigned to unsupported engine. - rocksdb doesn't support embedded server ebfc4e6ad02 so is excluded Closes PR #774 Reviewed by: serg@mariadb.com vicentiu@mariadb.org
* | Merge 10.4 into 10.5Marko Mäkelä2020-04-251-7/+7
|\ \ | |/ | | | | | | The functional changes of commit 5836191c8f0658d5d75484766fdcc3d838b0a5c1 (MDEV-21168) are omitted due to MDEV-742 having addressed the issue.
| * Merge 10.2 into 10.3Marko Mäkelä2020-04-151-7/+7
| |
* | unify "partitioning cannot do X" error messagesNikita Malyavin2020-03-311-1/+1
|/
* Merge 10.2 into 10.3Marko Mäkelä2019-03-271-1/+1
|
* MDEV-16429: Assertion `!table || (!table->read_set || ↵Nikita Malyavin2018-09-211-0/+9
| | | | | | | | | | | | | | | bitmap_is_set(table->read_set, field_index))' fails upon attempt to update virtual column on partitioned versioned table When using buffered sort in `UPDATE`, keyread is used. In this case, `TABLE::update_virtual_field` should be aborted, but it actually isn't, because it is called not with a top-level handler, but with the one that is actually going to access the disk. Here the problemm is issued with partitioning, so the solution is to recursively mark for keyread all the underlying partition handlers. * ha_partition: update keyread state for child partitions Closes #800
* Create 'main' test directory and move 't' and 'r' thereMichael Widenius2018-03-291-0/+1868