summaryrefslogtreecommitdiff
path: root/plugin
Commit message (Collapse)AuthorAgeFilesLines
...
| | * | | Merge 10.4 into 10.5Marko Mäkelä2022-07-271-2/+4
| | |\ \ \ | | | |/ /
| | | * | Merge branch '10.3' into 10.4Oleksandr Byelkin2022-07-271-2/+4
| | | |\ \ | | | | |/
| | | | * disks plugin: check for build prerequisites properlySergei Golubchik2022-07-261-2/+4
| | | | |
| * | | | Merge 10.5 into 10.6Marko Mäkelä2022-07-261-1/+1
| |\ \ \ \ | | |/ / /
| | * | | MDEV-28234 Change maturity of plugins for July 2022 ReleasesSergei Golubchik2022-07-051-1/+1
| | | | | | | | | | | | | | | | | | | | mysql_json: GAMMA -> STABLE
* | | | | MDEV-28838 password_reuse_check plugin mixes username and passwordOleksandr Byelkin2022-07-061-8/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To prevent the problem of mixing user name and password and host name and user name we add length of the hostname and user name to the hash.
* | | | | MDEV-27015 Assertion `!is_null()' failed in FixedBinTypeBundle<FbtImpl>::Fbt ↵bb-10.7-barAlexander Barkov2022-07-056-0/+169
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | FixedBinTypeBundle<FbtImpl>::Field_fbt::to_fbt() The assuption that Field::is_null() is always false when Field_fbt::val_native() or Field_fbt::to_fbt() are called was wrong. In some cases, e.g. when this helper Field method is called: inline String *val_str(String *str, const uchar *new_ptr) we temporarily reset Field::ptr to some alternative record buffer but don't reset null_ptr, so null_ptr still points to null flags of the original record. In such cases it's meaningless to test the original Field::null_ptr when Field::ptr is temporarily reset: they don't relate to each other. Removing the DBUG_ASSERT.
* | | | | Merge 10.6 into 10.7Marko Mäkelä2022-06-281-1/+1
|\ \ \ \ \ | |/ / / /
| * | | | Merge 10.5 into 10.6Marko Mäkelä2022-06-271-1/+1
| |\ \ \ \ | | |/ / /
| | * | | Merge 10.4 into 10.5Marko Mäkelä2022-06-271-1/+1
| | |\ \ \ | | | |/ /
| | | * | MDEV-28819 Statically compiled encryption plugins do not work in mariadb-backupVladislav Vaintroub2022-06-201-1/+1
| | | | | | | | | | | | | | | | | | | | Disable static build for encryption plugin file_key_management
* | | | | MDEV-28963 Incompatible data type assignment through SP vars is not ↵Alexander Barkov2022-06-2710-0/+1480
| | | | | | | | | | | | | | | | | | | | consistent with columns
* | | | | MDEV-28918 Implicit cast from INET6 UNSIGNED works differently on UPDATE vs ↵Alexander Barkov2022-06-2725-91/+2242
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ALTER Now INSERT, UPDATE, ALTER statements involving incompatible data type pairs, e.g.: UPDATE TABLE t1 SET col_inet6=col_int; INSERT INTO t1 (col_inet6) SELECT col_in FROM t2; ALTER TABLE t1 MODIFY col_inet6 INT; consistently return an error at the statement preparation time: ERROR HY000: Illegal parameter data types inet6 and int for operation 'SET' and abort the statement before starting interating rows. This error is the same with what is raised for queries like: SELECT col_inet6 FROM t1 UNION SELECT col_int FROM t2; SELECT COALESCE(col_inet6, col_int) FROM t1; Before this change the error was caught only during the execution time, when a Field_xxx::store_xxx() was called for the very firts row. The behavior was not consistent between various statements and could do different things: - abort the statement - set a column to the data type default value (e.g. '::' for INET6) - set a column to NULL A typical old error was: ERROR 22007: Incorrect inet6 value: '1' for column `test`.`t1`.`a` at row 1 EXCEPTION: Note, there is an exception: a multi-row INSERT..VALUES, e.g.: INSERT INTO t1 (col_a,col_b) VALUES (a1,b1),(a2,b2); checks assignment compability at the preparation time for the very first row only: (col_a,col_b) vs (a1,b1) Other rows are still checked at the execution time and return the old warnings or errors in case of a failure. This is done because catching all rows at the preparation time would change behavior significantly. So it still works according to the STRICT_XXX_TABLES sql_mode flags and the table transaction ability. This is too late to change this behavior in 10.7. There is no a firm decision yet if a multi-row INSERT..VALUES behavior will change in later versions.
* | | | | Merge 10.6 into 10.7Marko Mäkelä2022-06-072-1/+2
|\ \ \ \ \ | |/ / / /
| * | | | Merge remote-tracking branch 'origin/10.5' into 10.6Monty2022-06-063-3/+45
| |\ \ \ \ | | |/ / /
| | * | | MDEV-28491 Uuid. "UPDATE/DELETE" not working "WHERE id IN (SELECT id FROM ..)"bb-10.5-barAlexander Barkov2022-06-033-3/+45
| | | | | | | | | | | | | | | | | | | | This is a 10.5 version of the patch.
* | | | | MDEV-28491 Uuid. "UPDATE/DELETE" not working "WHERE id IN (SELECT id FROM ..)"Alexander Barkov2022-06-034-0/+73
| | | | | | | | | | | | | | | | | | | | This is a 10.7 version of the patch.
* | | | | Merge branch '10.6' into 10.7Sergei Golubchik2022-05-112-47/+56
|\ \ \ \ \ | |/ / / /
| * | | | Merge branch '10.5' into 10.6Sergei Golubchik2022-05-102-47/+56
| |\ \ \ \ | | |/ / /
| | * | | Merge branch '10.4' into 10.5Sergei Golubchik2022-05-092-47/+56
| | |\ \ \ | | | |/ /
| | | * | Merge branch '10.3' into 10.4Sergei Golubchik2022-05-081-1/+23
| | | |\ \ | | | | |/
| | | | * MDEV-28429 audit plugin report OOOOO.Alexey Botchkov2022-04-281-1/+23
| | | | | | | | | | | | | | | | | | | | | | | | | Few initializations to the connection_info structure added. I think they can be removed if we are sure the bug was fixed.
| | | * | MDEV-28431 auth_pam tool left zombie processes.Alexey Botchkov2022-04-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | The faulure in username packet reading can lead to the auth_plugin_tool zombie. So check and close the application.
| | | * | MDEV-26212 PAM authentication fails with ENOMEMSergei Golubchik2022-04-261-45/+32
| | | | | | | | | | | | | | | | | | | | | | | | | use posix_spawn(), not fork() - it's better for systems that don't overcommit memory
* | | | | Merge 10.6 into 10.7Marko Mäkelä2022-04-061-3/+5
|\ \ \ \ \ | |/ / / /
| * | | | Merge 10.5 into 10.6Marko Mäkelä2022-04-061-3/+5
| |\ \ \ \ | | |/ / /
| | * | | Merge 10.4 into 10.5Marko Mäkelä2022-04-061-3/+5
| | |\ \ \ | | | |/ /
| | | * | Merge 10.3 into 10.4Marko Mäkelä2022-04-061-3/+5
| | | |\ \ | | | | |/
| | | | * Adding a "const" qualifier to arguments of create_func(), create_native() etcAlexander Barkov2022-04-041-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "const" qualifier was obviously forgotten. This change will also simpily fixing of MDEV-27744.
* | | | | MDEV-27354 Change maturity of pluginsSergei Golubchik2022-04-024-6/+6
| | | | |
* | | | | Merge 10.6 into 10.7Marko Mäkelä2022-03-301-0/+6
|\ \ \ \ \ | |/ / / /
| * | | | Merge 10.5 into 10.6Marko Mäkelä2022-03-291-0/+6
| |\ \ \ \ | | |/ / /
| | * | | Merge 10.4 into 10.5Marko Mäkelä2022-03-291-0/+6
| | |\ \ \ | | | |/ /
| | | * | Merge 10.3 into 10.4Marko Mäkelä2022-03-291-0/+6
| | | |\ \ | | | | |/
| | | | * Merge 10.2 into 10.3Marko Mäkelä2022-03-291-0/+6
| | | | |\
| | | | | * MDEV-28177: server_audit; Update the offset of dbName on the aarch64 platform.hongdongjian2022-03-281-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On the aarch64 platform, MySQL 5.7.33 cannot install this version of the audit plugin, but X86_64 can run well。
* | | | | | Fix clang -Wtypedef-redefinitionMarko Mäkelä2022-03-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Include my_global.h before mysql.h so that the latter will not redefine my_socket and my_ulonglong. Fixup for commit 77c184df7c056da7364e606ac977cc2d3cd826ad
* | | | | | Merge 10.6 into 10.7Marko Mäkelä2022-03-081-1/+1
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge 10.5 into 10.6Vlad Lesin2022-03-071-1/+1
| |\ \ \ \ \ | | |/ / / /
| | * | | | MDEV-26230: mysql_upgrade fails to load type_mysql_json due to insufficientRucha Deodhar2022-03-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | maturity level Fix: Bumped maturity of the mysql_json plugin to gamma.
* | | | | | Merge branch '10.6' into 10.7Oleksandr Byelkin2022-02-046-18/+153
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge branch '10.5' into 10.6Oleksandr Byelkin2022-02-037-20/+159
| |\ \ \ \ \ | | |/ / / /
| | * | | | Merge branch '10.4' into 10.5Oleksandr Byelkin2022-02-011-0/+4
| | |\ \ \ \ | | | |/ / /
| | | * | | Merge branch '10.3' into 10.4Oleksandr Byelkin2022-01-304-12/+16
| | | |\ \ \ | | | | |/ /
| | | | * | Merge branch '10.2' into 10.3mariadb-10.3.33Oleksandr Byelkin2022-01-291-0/+4
| | | | |\ \ | | | | | |/
| | | | | * Fixed compiler error in auth_pam pluginMonty2022-01-201-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | Code copied from 10.6
| | | | * | MDEV-18918 SQL mode EMPTY_STRING_IS_NULL breaks RBR upon CREATE TABLE .. SELECTAlexander Barkov2022-01-253-12/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Removing DEFAULT from INFORMATION_SCHEMA columns. DEFAULT in read-only tables is rather meaningless. Upgrade should go smoothly. Also fixes: MDEV-20254 Problems with EMPTY_STRING_IS_NULL and I_S tables
| | * | | | MDEV-27668 Assertion `item->type_handler()->is_traditional_scalar_type() || ↵Alexander Barkov2022-01-283-2/+45
| | | | | | | | | | | | | | | | | | | | | | | | item->type_handler() == type_handler()' failed in Field_inet6::can_optimize_keypart_ref
| | * | | | MDEV-24487 Error after update to 10.5.8 on CentOS-8: DBD::mysql::st execute ↵Alexander Barkov2022-01-271-6/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | failed: Unknown MySQL error The problem happened because the the new client capability flag CLIENT_EXTENDED_METADATA was not put into the cache entry key. So results cached by a new client were sent to the old client (and vica versa) with a mis-matching metadata, which made the client abort the connection on an unexpected result set metadata packet format. The problem was caused by the patch for: MDEV-17832 Protocol: extensions for Pluggable types and JSON, GEOMETRY which forgot to adjust the query cache code. Fix: - Adding a new member Query_cache_query_flags::client_extended_metadata, so only clients with equal CLIENT_EXTENDED_METADATA flag values can reuse results. - Adding a new column CLIENT_EXTENDED_METADATA into INFORMATION_SCHEMA.QUERY_CACHE_INFO (privided by the qc_info plugin).
| | * | | | MDEV-18918 SQL mode EMPTY_STRING_IS_NULL breaks RBR upon CREATE TABLE .. SELECTAlexander Barkov2022-01-253-12/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The 10.5 version of the patch. Removing DEFAULT from INFORMATION_SCHEMA columns. DEFAULT in read-only tables is rather meaningless. Upgrade should go smoothly. Also fixes: MDEV-20254 Problems with EMPTY_STRING_IS_NULL and I_S tables
View Lorry Controller Status