Search Results
https://dev.mysql.com/doc/refman/8.4/en/upgrading-from-previous-series.html
When upgrading to MySQL 8.4.4 or later, it is recommended that you drop any spatial indexes beforehand, then re-create them after the upgrade is complete. Alternatively, you can drop and re-create such indexes immediately following the upgrade, but ... Before upgrading to MySQL 8.4, review the changes described in the following sections to identify those that apply to your current MySQL installation and ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.backup.html
240426 13:01:24 RDR1 INFO: Truncating binary log index '/home/meb/mysql/backup-temp/2024-04-26_13-01-23/datadir/binlog.index' to 16. In the following illustration, we back up an entire MySQL instance to a single file using the backup-to-image ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.html
During backup operations, mysqlbackup backs up: All InnoDB tables and indexes, including: The InnoDB system tablespace, which, by default contains all the InnoDB tables. In addition to creating backups, mysqlbackup can pack and unpack backup data, ... The mysqlbackup client is an easy-to-use tool for all backup and restore ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.usage.html
--log-bin-index Specifies the absolute path of the index file that lists all the binary log files. --relay-log-index Specifies the absolute path of the index file that lists all the relay log files. The following sections describe the command-line ...
https://dev.mysql.com/doc/relnotes/connector-j/en/news-9-3-0.html
(Bug #20279671) Calling get methods for CallableStatements resulted occasionally in ArrayIndexOutOfBoundsExceptions due to mismatches between the placeholder indexes and parameter indexes. (Bug #19857207) Connector/J failed to validate properly the ...(Bug #20802830) When using a CallableStatement to execute a stored procedure, a MySQLSyntaxErrorException was thrown if any parameter names contained an escaped ...
https://dev.mysql.com/doc/workbench/en/wb-configuration-additional.html
Safe Updates: When enabled (default), MySQL Workbench will not execute UPDATE or DELETE statements if a key is not defined in the WHERE clause. Related behavior: The Context Help right panel in the SQL editor displays documentation for SQL ...
https://dev.mysql.com/doc/workbench/en/wb-configuring-files.html
sql_history/ Directory SQL statements executed in the SQL editor are saved in the sql_history directory. They are stored as plain text files that are separated one per day (such as 2015-12-15) and they contain your MySQL Workbench SQL statement ...
https://dev.mysql.com/doc/workbench/en/wb-preferences-general-editors.html
The purpose of this option is to preserve the consistency of SQL statements within the document. This may potentially lead to inconsistencies in parsing of SQL statements stored in the document. Define the SQL statement delimiter to be different ...
https://dev.mysql.com/doc/workbench/en/wb-sql-editor-query-panel.html
You can enter SQL statements directly into the query editor area. The statements entered can be saved to a file or snippet for later use. At any point, you can also execute the statements you have entered. The SQL query secondary tab opens by ...
https://dev.mysql.com/doc/workbench/en/wb-tables-physical-schemata.html
Copy SQL to Clipboard: Copies a CREATE TABLE statement for the table. Copy Insert to Clipboard: Copies INSERT statements based on the model's inserts. Copy Insert Template to Clipboard: Copies a generic INSERT statement that is based on the model.