Search Results
                    
                    
            https://dev.mysql.com/doc/internals/en/cleaning-up-with-index-end.html
                                 The [custom-engine.html#custom-engine-api-reference-index_end index_end()] method is a counterpart to the index_init() method. The purpose of the index_end() method is to clean up any preparations made by the index_init() method. If a storage ...
                                            
                https://dev.mysql.com/doc/internals/en/index-read-last.html
                                Synopsis virtual int index_read_last ( buf, key, keypart_map); byte * buf ; const byte * key ; ulonglong keypart_map ; Description This is the index_read_last method. Parameters buf key keypart_map Return Values Usage This section is still to be ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/performance-schema-statement-tables.html
                                Statement events occur at a high level of the event hierarchy. Within the event hierarchy, wait events nest within stage events, which nest within statement events, which nest within transaction events. These tables store statement events: ...For ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/performance-schema-statement-digests.html
                                 The MySQL server is capable of maintaining statement digest information. The digesting process converts each SQL statement to normalized form (the statement digest) and computes a SHA-256 hash value (the digest hash value) from the normalized ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/create-table.html
                                For additional information about index prefixes, see Section 15.1.15, “CREATE INDEX Statement”. For general background in addition to the following descriptions, see Section 15.1.15, “CREATE INDEX Statement”, Section 15.1.20.5, “FOREIGN ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/sql-prepared-statements.html
                                Using prepared statements with placeholders for parameter values has the following benefits: Less overhead for parsing the statement each time it is executed. Typically, database applications process large volumes of almost-identical statements, ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/performance-schema-statement-summary-tables.html
                                 The Performance Schema maintains tables for collecting current and recent statement events, and aggregates that information in summary tables. Section 29.12.6, “Performance Schema Statement Event Tables” describes the events on which statement ...Each row summarizes events for a given account (user and host combination) and event ...
                                            
                https://dev.mysql.com/doc/c-api/8.4/en/c-api-prepared-statement-interface-usage.html
                                 To prepare and execute a statement, an application follows these steps: Create a prepared statement handler with mysql_stmt_init(). To prepare the statement on the server, call mysql_stmt_prepare() and pass it a string containing the SQL statement. 
                                            
                https://dev.mysql.com/doc/refman/8.4/en/statement-caching.html
                                 For certain statements that a client might execute multiple times during a session, the server converts the statement to an internal structure and caches that structure to be used during execution. Caching enables the server to perform more ...In ...
                                            MySQL 8.4 Reference Manual :: 19.2.1.3 Determination of Safe and Unsafe Statements in Binary Logging
                https://dev.mysql.com/doc/refman/8.4/en/replication-rbr-safe-unsafe.html
                                 The “safeness” of a statement in MySQL replication refers to whether the statement and its effects can be replicated correctly using statement-based format. If this is true of the statement, we refer to the statement as safe; otherwise, we ...