Search Results
https://dev.mysql.com/doc/workbench/en/wb-mforms.html
This further reduces the development effort because plugin developers can use MForms rather than writing front-end specific code for each supported platform. MySQL Workbench is implemented with a C++ core back-end, and a native front-end for each ...
Oracle Enterprise Manager for MySQL Database User's Guide :: 1.2 Obtaining and Installing the Plugin
https://dev.mysql.com/doc/mysql-em-plugin/en/myoem-obtaining-installing-upgrading.html
For instructions on how to obtain, install, upgrade, and deploy the plugin, consult the following Oracle Enterprise Manager documentation, https://docs.oracle.com/cd/E73210_01/EMADM/GUID-7FE4211E-711B-4926-AC18-DAB5C17E82BF.htm#EMADM109.
https://dev.mysql.com/doc/refman/8.4/en/clone-plugin-monitoring.html
memory/clone/data: Tracks memory allocated by the clone plugin during a clone operation. You can monitor the status and progress of a cloning operation on the recipient MySQL server instance using the clone_status and clone_progress Performance ...
https://dev.mysql.com/doc/internals/en/com-change-user-and-non-client-plugin-auth-clients.html
Clients which do not support pluggable authentication can send COM_CHANGE_USER command for accounts which use Secure Password Authentication or Old Password Authentication. In this case it is assumed that server has already sent the authentication ...
https://dev.mysql.com/doc/internals/en/non-client-plugin-auth-clients.html
The only situation where server will request authentication method change from a client which does not set CLIENT_PLUGIN_AUTH flag is when the following conditions hold: the client connects to an account which uses Old Password Authentication. the ...
https://dev.mysql.com/doc/refman/8.4/en/clone-plugin-compressed-data.html
The following requirements apply when cloning remote data: The recipient file system must support sparse files and hole punching for hole punching to occur on the recipient. The donor and recipient file systems must have the same block size. If file ...
https://dev.mysql.com/doc/refman/8.4/en/clone-plugin-concurrent-ddl.html
In MySQL 8.4, concurrent DDL is permitted on the donor by default. Concurrent DDL support on the donor is controlled by the clone_block_ddl variable. Concurrent DDL support can be enabled and disabled dynamically using a SET statement like this ...
https://dev.mysql.com/doc/refman/8.4/en/clone-plugin-directories.html
When data is cloned, the following directories and files are created for internal use. #ib_archive: Contains internally archived log files, archived on the donor during the cloning operation. *.#clone files: Temporary data files created on the ...
https://dev.mysql.com/doc/refman/8.4/en/clone-plugin-encrypted-data.html
The following requirements apply: A secure connection is required when cloning remote data to ensure safe transfer of unencrypted tablespace keys over the network. Tablespace keys are decrypted at the donor before transport and re-encrypted at the ...
https://dev.mysql.com/doc/refman/8.4/en/clone-plugin-failure-handling.html
This section describes failure handing at different stages of a cloning operation. If a failure occurs during the prerequisite check, the CLONE INSTANCE operation reports an error. Concurrent DDL on the donor is blocked only if the clone_block_ddl ...