Search Results
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-replication-conflict-resolution.html
Due to the fact that no timestamp is available for a delete operation, a delete using NDB$MAX() is in fact processed as NDB$OLD, but for some use cases, this is not optimal. Requirements Source Column Control Conflict Resolution Control Conflict ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-replication-schema.html
Important For insert conflict resolution using NDB$MAX_INS() or NDB$MAX_DEL_WIN_INS(), an SQL node (that is, a mysqld process) can record row updates on the source cluster as WRITE_ROW events with the --ndb-log-update-as-write option enabled for ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-command-options.html
Note The mysql client always passes optimizer hints to the server, regardless of whether this option is given. mysql supports the following options, which can be specified on the command line or in the [mysql] and [client] groups of an option file.
https://dev.mysql.com/doc/refman/8.4/en/mysql-configurator-cli.html
config-type N/A configuration-type list Developer, Server, Dedicated, Manual development configure, reconfigure N/A Optimizes system resources depending on the intended use of the server instance. MySQL Configurator supports GUI (default) and CLI ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-configurator-workflow-server.html
Manual: Prevents MySQL Configurator from attempting to optimize the server installation, and instead, sets the default values to the server variables included in the my.ini configuration file. MySQL Configurator performs the initial configuration, ...
https://dev.mysql.com/doc/refman/8.4/en/mysqldump.html
The mysqldump client utility performs logical backups, producing a set of SQL statements that can be executed to reproduce the original database object definitions and table data. It dumps one or more MySQL databases for backup or transfer to ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-limitations-storage-engines.html
OPTIMIZE PARTITION does not work correctly with partitioned tables that use InnoDB. In MySQL 8.4, partitioning support is not actually provided by the MySQL Server, but rather by a table storage engine's own or native partitioning handler. In MySQL ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-management-exchange.html
Table nt contains no foreign key references, and no other table has any foreign keys that refer to nt. There are no rows in nt that lie outside the boundaries of the partition definition for p. For InnoDB tables, both tables must use the same row ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-overview.html
Some queries can be greatly optimized in virtue of the fact that data satisfying a given WHERE clause can be stored only on one or more partitions, which automatically excludes any remaining partitions from the search. This section provides a ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-types.html
This section discusses the types of partitioning which are available in MySQL 8.4. This type of partitioning assigns rows to partitions based on column values falling within a given range. For information about an extension to this type, RANGE ...