Search Results
https://dev.mysql.com/doc/internals/en/myisam-column-attributes.html
Some further random notes about the new format: In old tables (from MySQL 4.1 and earlier), VARCHAR columns have type MYSQL_TYPE_VAR_STRING, which works exactly like a CHAR with the exception that if you do an ALTER TABLE, it's converted to a true ... Next I'll describe the physical attributes of each column in a ...
https://dev.mysql.com/doc/internals/en/optimizer-early-nulls-filtering.html
Suppose further that table tblY is accessed via ref or eq_ref access on tblY.key_column = tblX.column or, in the case of ref access using multiple key parts, via ... We make the following inference: (tblY.key_partN = tblX.column) => (tblX.column IS ... Suppose we have a join order such as this one: ..., tblX, ..., tblY, ...
https://dev.mysql.com/doc/internals/en/replication-correct.html
For purposes of defining "correct replication", the tables are considered equal if they are equal on the common columns. Note: For purposes of defining "correct replication", the tables are considered equal if they are equal on the common columns.
https://dev.mysql.com/doc/internals/en/store-lock.html
The idea with handler::store_lock() is the following: The statement decided which locks we should need for the table for updates/deletes/inserts we get WRITE locks, for SELECT... Before adding the lock into the table lock handler mysqld calls store ...Synopsis virtual THR_LOCK_DATA ** store_lock ( thd, to, lock_type); THD * thd ; THR_LOCK_DATA ** to ; enum thr_lock_type lock_type ; Description This is the store_lock ...
https://dev.mysql.com/doc/internals/en/unsafe-statements.html
Update from a sub-statement of a table that has an autoincrement column. This is unsafe because the Intvar_log_event is limited to only hold autoincrement values for one table. Statements referencing system log tables, since the contents of those ...
https://dev.mysql.com/doc/internals/en/variation-of-storage-engine.html
Checks of the INFORMATION_SCHEMA The storage engines to be used for information_schema tables are hardcoded. when selecting on INFORMATION_SCHEMA tables should not run with storage engine variations. That means mostly: DO NOT use hardcoded storage ...Therefore tests focussed on permissions, optimizer strategies, column data types ...
https://dev.mysql.com/doc/ndbapi/en/ndb-examples-basic-delete.html
This example shows deleting a row from a table already created and populated previously (see Section 2.5.1.2, “NDB API Basic Insertion Example”). It performs the deletion using a single NdbOperation within a transaction, and handles errors ...
https://dev.mysql.com/doc/ndbapi/en/ndb-examples-event-handling.html
#include <NdbApi.hpp> // Used for cout #include <stdio.h> #include <iostream> #include <unistd.h> #ifdef VM_TRACE #include <my_global.h> #endif #ifndef assert #include <assert.h> #endif /** * Assume that there is a table which is being updated by * ...The source code for this program may be found in the NDB Cluster source tree, in the file ...
https://dev.mysql.com/doc/ndbapi/en/ndb-examples-secondary-indexes.html
This program illustrates how to use secondary indexes in the NDB API. The source code for this example may be found in the NDB Cluster source tree, in storage/ndb/ndbapi-examples/ndbapi_simple_index/main.cpp.
https://dev.mysql.com/doc/ndbapi/en/ndb-nodejs-api-mynode.html
You can get the mapping either by name, or by using an existing mapping: TableMapping(tableName); TableMapping(tableMapping); openSession(properties, mappings, Function(err, Session) callback); Connect to the data source and get a Session in the ...