Search Results
https://dev.mysql.com/doc/refman/8.4/en/serialized-dictionary-information.html
For InnoDB, an SDI record requires a single index page, which is 16KB in size by default. The IMPORT TABLE statement imports MyISAM tables based on information contained in .sdi files. In addition to storing metadata about database objects in the ...
https://dev.mysql.com/doc/refman/8.4/en/structured-system-variables.html
(You could also have written --default.key_buffer_size=256K.) In addition, the server creates a second key cache named extra_cache that has a size of 128KB, with the size of block buffers for caching table index blocks set to 2048 bytes. For ... A ...
https://dev.mysql.com/doc/refman/8.4/en/using-log-files.html
You can also try the command EXPLAIN on all SELECT statements that takes a long time to ensure that mysqld is using indexes properly. Note that before starting mysqld with the general query log enabled, you should check all your tables with ...
https://dev.mysql.com/doc/mysql-ai/9.5/en/mys-ai-bulk-load-limitations.html
It cannot execute when the target table is explicitly locked by a LOCK TABLES statement. LOAD DATA with ALGORITHM=BULK supports tables with at least one column with the VECTOR data type. If you attempt to load a table without at least one column ...
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.
https://dev.mysql.com/doc/workbench/en/wb-what-is-new-63.html
SQL Editor Auto-Completion The SQL editor auto-completion improvements include the following changes: It now functions with all statement types, when before only SELECT statements were fully supported. This new wizard does not require an executed ...