Search Results
https://dev.mysql.com/doc/relnotes/connector-j/en/news-8-0-11.html
Functionality Added or Changed Bugs Fixed Functionality Added or Changed X DevAPI: The locking options lockShared() and lockExclusive(), available when retrieving data from collection.find() and table.select(), now also accept an optional locking ...
https://dev.mysql.com/doc/relnotes/connector-j/en/news-9-1-0.html
(Bug #108415, Bug #34579258) When adding a long SQL string to a batched Statement, if the string's length was greater than the value of maxAllowedPacket, an ArrayIndexOutOfBoundsException was thrown. (Bug #36936407) When using PreparedStatements, ...
https://dev.mysql.com/doc/mysql-ai/9.5/en/mys-ai-genai-vector-store-overview.html
However, for query offload to be successful, the vector table must be offloaded to AI engine using the SECONDARY_LOAD clause with the ALTER TABLE statement, and the query (SELECT statement) must use at least one vector function in the SELECT LIST, ... This section describes the Vector Store functionality available with ...
https://dev.mysql.com/doc/ndbapi/en/ndb-ndbdictionary.html
This section provides information about the NdbDictionary class, which stores meta-information about NDB database objects, such as tables, columns, and indexes. NdbDictionary Class Overview NdbDictionary::AutoGrowSpecification ...While the ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-limits.html
This section describes limits for InnoDB tables, indexes, tablespaces, and other aspects of the InnoDB storage engine. The index key prefix length limit is 3072 bytes for InnoDB tables that use DYNAMIC or COMPRESSED row format. The index key prefix ...ERROR 1070 (42000): Too many key parts specified; max 16 parts allowed The maximum row size, excluding any variable-length columns that are stored off-page, is slightly less than half of a page for 4KB, 8KB, 16KB, and 32KB page ...
https://dev.mysql.com/doc/refman/8.4/en/online-ddl-parallel-thread-configuration.html
The actual number of threads that scan the clustered index is the number defined by the innodb_parallel_read_threads setting or the number of index subtrees to scan, whichever is smaller. The following limitations apply: Parallel threads are not ...
https://dev.mysql.com/doc/refman/8.4/en/optimizing-memory-tables.html
On the CREATE INDEX statement, use the clause USING BTREE or USING HASH. For best performance with MEMORY tables, examine the kinds of queries against each table, and specify the type to use for each associated index, either a B-tree index or a hash ... Consider using MEMORY tables for noncritical data that is accessed often, and is read-only or rarely ...
https://dev.mysql.com/doc/refman/8.4/en/optimizing-spatial-analysis.html
Other storage engines support non-SPATIAL indexes, as described in Section 15.1.15, “CREATE INDEX Statement”. For MyISAM and InnoDB tables, search operations in columns containing spatial data can be optimized using SPATIAL indexes. The most ...
https://dev.mysql.com/doc/relnotes/connector-cpp/en/news-8-0-17.html
(WL #12721) X DevAPI Notes For index specifications passed to the Collection::createIndex() method (for X DevAPI applications) or the mysqlx_collection_create_index() function (for X DevAPI for C applications), Connector/C++ now supports indexing ...
https://dev.mysql.com/doc/internals/en/com-refresh.html
Note As of MySQL 5.7.11, COM_REFRESH is deprecated and will be removed in a future version of MySQL.