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/ansi-diff-foreign-keys.html
In an SQL statement that inserts, deletes, or updates many rows, foreign key constraints (like unique constraints) are checked row-by-row. In that case, a (child table) row containing such a foreign key can be inserted even though it does not match ...For example, if you define a RESTRICT type constraint, and there is a child row with several parent rows, InnoDB does not permit the deletion of any of the parent ...
https://dev.mysql.com/doc/refman/5.7/en/char.html
For truncation of nonspace characters, you can cause an error to occur (rather than a warning) and suppress insertion of the value by using strict SQL mode. For VARCHAR columns, trailing spaces in excess of the column length are truncated prior to ... The CHAR and VARCHAR types are similar, but differ in the way they are stored and ...
https://dev.mysql.com/doc/refman/5.7/en/enum.html
If strict SQL mode is enabled, attempts to insert invalid ENUM values result in an error. An ENUM is a string object with a value chosen from a list of permitted values that are enumerated explicitly in the column specification at table creation ...
https://dev.mysql.com/doc/refman/5.7/en/faqs-triggers.html
Does MySQL have statement-level or row-level triggers? All triggers are FOR EACH ROW; that is, the trigger is activated for each row that is inserted, updated, or deleted. For example, consider a table EMP that has an AFTER insert trigger, which ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-consistent-read.html
If you insert or modify some rows and then commit that transaction, a DELETE or UPDATE statement issued from another concurrent REPEATABLE READ transaction could affect those just-committed rows, even though the session could not query them. In the ... A consistent read means that InnoDB uses multi-versioning to present to a query a snapshot of the database at a point in ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-replication.html
2013-09-24T13:04:38.639684Z 49 [Note] Slave I/O thread: connected to master 'root@localhost:13000', replication started in log '0.000001' at position 114 Testing the InnoDB memcached Replication Configuration This example demonstrates how to test ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html
For other search conditions, InnoDB locks the index range scanned, using gap locks or next-key locks to block insertions by other sessions into the gaps covered by the range. It is not recommended to mix locking statements (UPDATE, INSERT, DELETE, ... Transaction isolation is one of the foundations of database ...
https://dev.mysql.com/doc/refman/5.7/en/merge-table-problems.html
The INSERT_METHOD table option for a MERGE table indicates which underlying MyISAM table to use for inserts into the MERGE table. However, use of the AUTO_INCREMENT table option for that MyISAM table has no effect for inserts into the MERGE table ...
https://dev.mysql.com/doc/refman/5.7/en/migrating-from-year2.html
Values outside the range from 1970 to 2069 are stored incorrectly when inserted into a YEAR(2) column in a CSV table. For example, inserting 2211 results in a display value of 11 but an internal value of 2011. Consequently, the following operations ... This section describes problems that can occur when using the 2-digit YEAR(2) data type and provides information about converting existing YEAR(2) columns to 4-digit year-valued columns, which can be declared as YEAR with an implicit display width of 4 characters, or equivalently as YEAR(4) with an explicit display ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations.html
Reads from such tables are relatively unaffected; pending INSERT and UPDATE operations are performed as soon as the partitioning operation has completed. This section discusses current restrictions and limitations on MySQL partitioning support. The ...