PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/gis-data-formats.html
Two standard spatial data formats are used to represent geometry objects in queries: Well-Known Text (WKT) format Well-Known Binary (WKB) format Internally, MySQL stores geometry values in a format that is not identical to either WKT or WKB format.
https://dev.mysql.com/doc/refman/8.0/en/gis-wkb-functions.html
These functions take as arguments a BLOB containing a Well-Known Binary (WKB) representation and, optionally, a spatial reference system identifier (SRID). For a description of WKB format, see Well-Known Binary (WKB) Format. Functions in this ...
https://dev.mysql.com/doc/refman/8.0/en/gone-away.html
If you need big queries (for example, if you are working with big BLOB columns), you can increase the query limit by setting the server's max_allowed_packet variable, which has a default value of 64MB. This section also covers the related Lost ...
https://dev.mysql.com/doc/refman/8.0/en/hexadecimal-literals.html
The 0x notation is based on ODBC, for which hexadecimal strings are often used to supply values for BLOB columns. Hexadecimal literal values are written using X'val' or 0xval notation, where val contains hexadecimal digits (0..9, A..F). Lettercase ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-columns-table.html
1 = VARCHAR, 2 = CHAR, 3 = FIXBINARY, 4 = BINARY, 5 = BLOB, 6 = INT, 7 = SYS_CHILD, 8 = SYS, 9 = FLOAT, 10 = DOUBLE, 11 = DECIMAL, 12 = VARMYSQL, 13 = MYSQL, 14 = GEOMETRY. For related usage information and examples, see Section 17.15.3, “InnoDB ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-statistics-table.html
However, prefix lengths for index specifications in CREATE TABLE, ALTER TABLE, and CREATE INDEX statements are interpreted as number of characters for nonbinary string types (CHAR, VARCHAR, TEXT) and number of bytes for binary string types (BINARY, ...The information_schema_stats_expiry system variable defines the period of time before cached table statistics ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-tables-table.html
Notes For NDB tables, the output of this statement shows appropriate values for the AVG_ROW_LENGTH and DATA_LENGTH columns, with the exception that BLOB columns are not taken into account. The information_schema_stats_expiry system variable defines ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-benefits.html
The storage layout for table data is more efficient for BLOB and long text fields, with the DYNAMIC row format. InnoDB tables have the following benefits: If the server unexpectedly exits because of a hardware or software issue, regardless of what ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-usage.html
This setting may still be useful for tables with many long BLOB, VARCHAR or TEXT columns, because such values often do compress well, and might therefore require fewer overflow pages as described in Section 17.9.1.5, “How Compression Works for ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-file-space.html
LONGBLOB and LONGTEXT columns must be less than 4GB, and the total row length, including BLOB and TEXT columns, must be less than 4GB. The data files that you define in the configuration file using the innodb_data_file_path configuration option ...