PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/problems-with-null.html
For example, the following statements are completely different: mysql> INSERT INTO my_table (phone) VALUES (NULL); mysql> INSERT INTO my_table (phone) VALUES (''); Both statements insert a value into the phone column, but the first inserts a NULL ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-lifecycle.html
Whenever the binary log is rotated or the server is shut down, the server writes GTIDs for all transactions that were written into the previous binary log file into the mysql.gtid_executed table. Whenever the binary log is rotated or the server is ... The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the replication source ...
https://dev.mysql.com/doc/refman/5.7/en/replication-options-binary-log.html
Rows are grouped into events smaller than this size if possible. However, problems arise when modifications done to nontransactional tables on behalf of a transaction become immediately visible to other connections because these changes may not be ... Startup Options Used with Binary Logging System Variables Used with Binary Logging You can use the mysqld options and system variables that are described in this section to affect the operation of the binary log as well as to control which statements are written to the binary ...
https://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html
Storing the string also results in slower comparisons because of the larger values and the need to take character set collation rules into account. For example: INSERT INTO t VALUES (1,AES_ENCRYPT('text',UNHEX('F3229A0B371ED2D9441B830D21A390C3'))); ...If you want to store these results, use a column with a VARBINARY or BLOB binary string data ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-hash.html
In addition, you most likely want to follow this with PARTITIONS num, where num is a positive integer representing the number of partitions into which the table is to be divided. Partitioning by HASH is used primarily to ensure an even distribution ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations.html
In MySQL 5.7, key caches are supported for partitioned MyISAM tables, using the CACHE INDEX and LOAD INDEX INTO CACHE statements. Key caches may be defined for one, several, or all partitions, and indexes for one, several, or all partitions may be ... This section discusses current restrictions and limitations on MySQL partitioning ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-management-exchange.html
To see how this occurs, first insert a row into e2 that is outside the boundaries of the partition definition for partition p0 of table e. Table nt contains no foreign key references, and no other table has any foreign keys that refer to nt. There ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-functions.html
On server2, extract that statement from the mysqldump output, and store the GTID set into a local variable, such as $gtid_purged_set. To check, on server1, extract and store gtid_purged from the output into a local variable as done previously, then ... This section provides examples of stored functions (see Chapter 23, Stored Objects) which you can create using some of the built-in functions provided by MySQL for use with GTID-based replication, listed here: GTID_SUBSET(): Shows whether one GTID set is a subset of ...
https://dev.mysql.com/doc/refman/5.7/en/upgrading-from-previous-series.html
Example: SET sql_mode = ''; CREATE TABLE t (d DATE DEFAULT 0); SET sql_mode = 'NO_ZERO_DATE,STRICT_ALL_TABLES'; INSERT INTO t (d) VALUES(DEFAULT); In this case, 0 should be accepted for the CREATE TABLE but rejected for the INSERT. In the example, ... Before upgrading to MySQL 5.7, review the changes described in this section to identify those that apply to your current MySQL installation and ...
https://dev.mysql.com/doc/refman/5.7/en/using-date.html
You should use this format in UPDATE expressions and in the WHERE clause of SELECT statements. For example: SELECT * FROM t1 WHERE date >= '2003-05-05'; As a convenience, MySQL automatically converts a date to a number if the date is used in numeric ...