Whether a name can be given to a column, by a Rename now and by later
operations that make columns (PLAN §11.4, replacing the spec's
/^[A-Za-z0-9_ ]{1,100}$/u, Appendix A): not empty, no space at either
end, no " (which breaks the column's SQL alias), no \ (the engine then
can't find the column again), no backtick (Databricks and MemSQL quote names
with backticks, and the engine escapes none, PLAN §11.14), no control
character, and at most MAX_COLUMN_NAME_LENGTH code points. Spaces,
hyphens, single quotes and non-ASCII letters are fine.
Whether a name can be given to a column, by a Rename now and by later operations that make columns (PLAN §11.4, replacing the spec's
/^[A-Za-z0-9_ ]{1,100}$/u, Appendix A): not empty, no space at either end, no"(which breaks the column's SQL alias), no\(the engine then can't find the column again), no backtick (Databricks and MemSQL quote names with backticks, and the engine escapes none, PLAN §11.14), no control character, and at mostMAX_COLUMN_NAME_LENGTHcode points. Spaces, hyphens, single quotes and non-ASCII letters are fine.