Syntax\n------\n\nCOLUMN_GET(dyncol_blob, column_nr as type)\nCOLUMN_GET(dyncol_blob, column_name as type)\n\nDescription\n-----------\n\nGets the value of a dynamic column by its name. If no column with the given name exists, NULL will be returned.\n\ncolumn_name as type requires that one specify the datatype of the dynamic column they are reading.\n\nThis may seem counter-intuitive: why would one need to specify which datatype they're retrieving? Can't the dynamic columns system figure the datatype from the data being stored?\n\nThe answer is: SQL is a statically-typed language. The SQL interpreter needs to know the datatypes of all expressions before the query is run (for example, when one is using prepared statements and runs "select COLUMN_GET(...)", the prepared statement API requires the server to inform the client about the datatype of the column being read before the query is executed and the server can see what datatype the column actually has).\n\nLengths\n\nSuppose running a query like this:\n\n``sql\nSELECT COLUMN_GET(BLOB, 'colname' AS CHAR) ...\n`\n\nWithout specifying a maximum length (i.e. using as CHAR, not as CHAR(n)`), MariaDB will report the maximum length of the result set column to be 16,777,216. This may cause excessive memory usage in some client libraries, because they try to pre-allocate a buffer of maximum result set width. To avoid this problem, use CHAR(n) whenever you're using COLUMN_GET in the select list.\n\nSee Dynamic Columns:Datatypes for more information about datatypes.\n\nURL: https://mariadb.com/docs/server/reference/sql-functions/special-functions/dynamic-columns-functions/column_get