Spaltentypen in MySQL

data_type:
    BIT[(length)]
  | TINYINT[(length)] [UNSIGNED]
  | SMALLINT[(length)] [UNSIGNED]
  | MEDIUMINT[(length)] [UNSIGNED]
  | INT[(length)] [UNSIGNED]
  | INTEGER[(length)] [UNSIGNED] 
  | BIGINT[(length)] [UNSIGNED] 
  | DOUBLE[(length,decimals)] [UNSIGNED]
  | DECIMAL[(length[,decimals])] [UNSIGNED] 
  | DATE              "2020-10-04"
  | TIME              "17:10:33" 
  | DATETIME          "2020-10-04 17:10:33"
  | YEAR
  | CHAR[(length)] [CHARACTER SET charset_name] [COLLATE collation_name]
  | VARCHAR(length) [CHARACTER SET charset_name] [COLLATE collation_name]
  | TINYBLOB
  | BLOB
  | MEDIUMBLOB
  | LONGBLOB
  | TINYTEXT [CHARACTER SET charset_name] [COLLATE collation_name]
  | TEXT [CHARACTER SET charset_name] [COLLATE collation_name]
  | MEDIUMTEXT [CHARACTER SET charset_name] [COLLATE collation_name]
  | LONGTEXT  [CHARACTER SET charset_name] [COLLATE collation_name]
  | ENUM(value1,value2,value3,...) [CHARACTER SET charset_name] [COLLATE collation_name]
  | SET(value1,value2,value3,...) [CHARACTER SET charset_name] [COLLATE collation_name]

vgl.: »TIME('04:20:00')« als Funktion, die einen Zeitwert ergibt

INT(length) - length ist nur die Anzeigebreite, ohne Einfluß auf die speicherbaren Werte

Die Verwendung von »VARCHAR« setzt Transitional SQL-92  voraus, bei Entry-Level SQL-92  müßte statt dessen »CHAR« verwendet werden.

`releaseDatePrecision` enum("Y","YM","YMD"), --- besser Nachschlagetabelle?