https://dev.mysql.com/federated-usagenotes.html
For example, creating a FEDERATED table with an index prefix on VARCHAR, TEXT or BLOB columns will fail. The following items indicate features that the FEDERATED storage engine does and does not support: The remote server must be a MySQL server. The ...
https://dev.mysql.com/fetching-spatial-data.html
SELECT ST_AsText(g) FROM geom; Fetching spatial data in WKB format: The ST_AsBinary() function converts a geometry from internal format to a BLOB containing the WKB value. Geometry values stored in a table can be fetched in internal format.
https://dev.mysql.com/general-thread-states.html
For the end state, the following operations could be happening: Writing an event to the binary log Freeing memory buffers, including for blobs Killed Someone has sent a KILL statement to the thread and it should abort next time it checks the kill ...
https://dev.mysql.com/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/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/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/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/innodb-benefits.html
The storage layout for table data is more efficient for BLOB and long text fields, with the DYNAMIC row format. You may find InnoDB tables beneficial for the following reasons: If your server crashes because of a hardware or software issue, ...
https://dev.mysql.com/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 15.14.3, “InnoDB ...
https://dev.mysql.com/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 15.9.1.5, “How Compression Works for ...
