Search Results
                    
                    
            https://dev.mysql.com/doc/refman/8.4/en/analyze-table.html
                                ANALYZE [NO_WRITE_TO_BINLOG | LOCAL] TABLE tbl_name UPDATE HISTOGRAM ON col_name [, col_name] ... [WITH N BUCKETS] [{MANUAL | AUTO} UPDATE] ANALYZE [NO_WRITE_TO_BINLOG | LOCAL] TABLE tbl_name UPDATE HISTOGRAM ON col_name [USING DATA 'json_data'] ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/archive-storage-engine.html
                                 The ARCHIVE storage engine produces special-purpose tables that store large amounts of unindexed data in a very small footprint. To enable this storage engine if you build MySQL from source, invoke CMake with the -DWITH_ARCHIVE_STORAGE_ENGINE ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/atomic-ddl.html
                                An atomic DDL statement combines the data dictionary updates, storage engine operations, and binary log writes associated with a DDL operation into a single, atomic operation. The operation is either committed, with applicable changes persisted to ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/backup-types.html
                                 This section describes the characteristics of different types of backups. Physical (Raw) Versus Logical Backups Physical backups consist of raw copies of the directories and files that store database contents. This type of backup is suitable for ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/binary-log.html
                                 The binary log contains “events” that describe database changes such as table creation operations or changes to table data. It also contains events for statements that potentially could have made changes (for example, a DELETE which matched no ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/binary-varbinary.html
                                 The BINARY and VARBINARY types are similar to CHAR and VARCHAR, except that they store binary strings rather than nonbinary strings. This means they have the binary character set and collation, and comparison and sorting are based on the numeric ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/binlog-replication-configuration-overview.html
                                 This section describes replication between MySQL servers based on the binary log file position method, where the MySQL instance operating as the source (where the database changes take place) writes updates and changes as “events” to the binary ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/blob.html
                                 A BLOB is a binary large object that can hold a variable amount of data. These differ only in the maximum length of the values they can hold. These correspond to the four BLOB types and have the same maximum lengths and storage requirements. They ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/built-in-function-reference.html
                                 The following table lists each built-in (native) function and operator and provides a short description of each one. For a table listing functions that are loadable at runtime, see Section 14.2, “Loadable Function Reference”. ->> Return value ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/channels-naming-conventions.html
                                 This section describes how naming conventions are impacted by replication channels. Each replication channel has a unique name which is a string with a maximum length of 64 characters and is case-insensitive. Because channel names are used in the ...