Nullable TIMESTAMP columns in MySQL are not nullable.
I noticed that in MySQL, if you add a TIMESTAMP column without specifying NULL or NOT NULL it defaults to NOT NULL which is backwards from every other type.
If I specify <constraints nullable="true"/> for TIMESTAMP columns in the Liquibase changelog, then load it into an HSQL database and do a diff against an empty MySQL database, the SQL output that it uses to create the table specifies "columnName TIMESTAMP" instead of "columnName TIMESTAMP NULL".
Would it be hard to change it so that the SQL script generated by Diff always specifies 'NULL' for nullable columns?
Put change into 3.0.5 to make mysql timestamp columns follow the same conventions as all other data types