PDF (US Ltr)
- 41.8Mb
PDF (A4)
- 41.9Mb
Man Pages (TGZ)
- 272.4Kb
Man Pages (Zip)
- 378.4Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/storage-requirements.html
This figure excludes BLOB or TEXT columns, which contribute only 9 to 12 bytes toward this size. For BLOB and TEXT data, the information is stored internally in a different area of memory than the row buffer. For example, storage for a MEDIUMTEXT ...
https://dev.mysql.com/doc/refman/9.7/en/alter-table.html
| ADD {FULLTEXT | SPATIAL} [INDEX | KEY] [index_name] (key_part,...) [index_option] ... (Adding or changing an SRID attribute requires a rebuild, and cannot be done in place, because the server must verify that all values have the specified SRID ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-compression-internals.html
The compression of B-tree nodes (of both clustered and secondary indexes) is handled differently from compression of overflow pages used to store long VARCHAR, BLOB, or TEXT columns, as explained in the following sections. Compressing BLOB, VARCHAR, ... This section describes some internal implementation details about compression for InnoDB ...
https://dev.mysql.com/doc/refman/9.7/en/load-data.html
Security Requirements For a non-LOCAL load operation, the server reads a text file located on the server host, so these security requirements must be satisfied: You must have the FILE privilege. For a LOCAL load operation, the client program reads a ...The file can be read from the server host or the client host, depending on whether the LOCAL modifier is ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-limitations-transactions.html
NDBCLUSTER stores only part of a column value that uses any of MySQL's BLOB or TEXT data types in the table visible to MySQL; the remainder of the BLOB or TEXT is stored in a separate internal table that is not accessible to MySQL. This issue does ... A number of limitations exist in NDB Cluster with regard to the handling of ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-programs-ndb-restore.html
These differences can be combined with other schema differences supported by ndb_restore, including changes to blob and text columns requiring the use of staging tables. --fields-optionally-enclosed-by Command-Line Format ... The NDB Cluster ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-programs-ndb-top.html
Output is available as plain text or an ASCII graph; you can specify this using the --text (-x) and --graph (-g) options, respectively. This option or --text must be true; both options may be true. (Formerly, the short form for this option was -t, ... ndb_top displays running information in the terminal about CPU usage by NDB threads on an NDB Cluster data ...
https://dev.mysql.com/doc/refman/9.7/en/mysqlimport.html
Invoke mysqlimport like this: mysqlimport [options] db_name textfile1 [textfile2 ...] For each text file named on the command line, mysqlimport strips any extension from the file name and uses the result to determine the name of the table into which ... The mysqlimport client provides a command-line interface to the LOAD DATA SQL ...
https://dev.mysql.com/doc/refman/9.7/en/manual-info.html
Differences between minor versions of MySQL 9.7 are noted in the present text with reference to release numbers (9.7.x). Typographical and Syntax Conventions This manual uses certain typographical conventions: Text in this style is used for SQL ...
https://dev.mysql.com/doc/refman/9.7/en/create-table-ndb-comment-options.html
This works for BLOB, MEDIUMBLOB, LONGBLOB, TEXT, MEDIUMTEXT, LONGTEXT, and JSON columns. NDB_COLUMN comments do not support TINYBLOB or TINYTEXT columns, since these have an inline part (only) of fixed size, and no separate parts to store elsewhere.