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/innodb-benefits.html
Truncating a file-per-table tablespace is very fast and can free up disk space for the operating system to reuse rather than only InnoDB. InnoDB tables have the following benefits: If the server unexpectedly exits because of a hardware or software ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-file-space.html
For tables stored this way, there is less fragmentation within the disk file, and when the table is truncated, the space is returned to the operating system rather than still being reserved by InnoDB within the system tablespace. The data files ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-porting-mysql.html
Too-long values in a string column such as a VARCHAR are truncated by removing some characters, which could produce nonsensical numeric values. Consider these aspects of memcached applications when adapting an existing MySQL schema or application ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-migration.html
This section describes techniques for moving or copying some or all InnoDB tables to a different server or instance. For example, you might move an entire MySQL instance to a larger, faster server; you might clone an entire MySQL instance to a new ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-operations.html
DISCARD PARTITION No No Only permits ALGORITHM=DEFAULT, LOCK=DEFAULT IMPORT PARTITION No No Only permits ALGORITHM=DEFAULT, LOCK=DEFAULT TRUNCATE PARTITION Yes Yes Does not copy existing data. Online support details, syntax examples, and usage ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-system-tablespace.html
Unlike the system tablespace, file-per-table tablespaces return disk space to the operating system when they are truncated or dropped. The system tablespace is the storage area for the InnoDB data dictionary, the doublewrite buffer, the change ...
https://dev.mysql.com/doc/refman/5.7/en/insert.html
INSERT [LOW_PRIORITY | DELAYED | HIGH_PRIORITY] [IGNORE] [INTO] tbl_name [PARTITION (partition_name [, partition_name] ...)] [(col_name [, col_name] ...)] {VALUES | VALUE} (value_list) [, (value_list)] ... [ON DUPLICATE KEY UPDATE assignment_list] ...
https://dev.mysql.com/doc/refman/5.7/en/json.html
The conversion to number should produce a meaningful result for JSON values that are numeric scalars, although (depending on the values) truncation and loss of precision may occur. The JSON data type provides these advantages over storing ...
https://dev.mysql.com/doc/refman/5.7/en/keyring-functions-general-purpose.html
A key value longer than that length can be stored using a keyring service function (see Section 5.5.6.2, “The Keyring Service”), but if retrieved using keyring_key_fetch() is truncated to the general keyring function limit. MySQL Server ...
https://dev.mysql.com/doc/refman/5.7/en/keywords.html
Certain keywords, such as SELECT, DELETE, or BIGINT, are reserved and require special treatment for use as identifiers such as table and column names. This may also be true for the names of built-in functions. Reserved words are permitted as ...