Sqlite timestamps using ALTER TABLE broken

[sitedyno]

From here; https://www.sqlite.org/lang_altertable.html

4. ALTER TABLE ADD COLUMN
   ...

• The column may not have a default value of CURRENT_TIME, CURRENT_DATE, CURRENT_TIMESTAMP, or an expression in parentheses.

└─[0] <git:(update-to-4.0.7 2065ce9 ✈ )> sqlite3 my_app "select * from taxonomies;"
1||1|1|1|2|(datetime(CURRENT_TIMESTAMP, 'utc'))|
2||2|1|3|4|(datetime(CURRENT_TIMESTAMP, 'utc'))|
3||3|2|1|2|(datetime(CURRENT_TIMESTAMP, 'utc'))|
└─[1] <git:(update-to-4.0.7 2065ce9 ✈ )> sqlite3 my_app ".schema taxonomies"
CREATE TABLE IF NOT EXISTS "taxonomies" (`id` INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, `parent_id` INTEGER NULL, `term_id` INTEGER NULL, `vocabulary_id` INTEGER NULL, `lft` INTEGER NULL, `rght` INTEGER NULL, `created` TIMESTAMP_TEXT NOT NULL DEFAULT '(datetime(CURRENT_TIMESTAMP, ''utc''))', `modified` TIMESTAMP_TEXT NULL, CONSTRAINT `fk_taxonomies2terms`, CONSTRAINT `fk_taxonomies2vocabularies`);

This (datetime(CURRENT_TIMESTAMP, 'utc')) is fine for CREATE TABLE, but not allowed for ALTAR TABLE :(

This only effects croogo/croogo/Taxonomy/config/Migrations/20191120012924_TaxonomySyncTimestampFields.php

I think the only way to work around this is by making another Migration (only for Sqlite) that creates new tables, copies data to the new table, drops the old table, then renames the new table to the old one. I will try to do a pull request if this sounds acceptable.

[rchavik]

If it only affects sqlite, should we bother? Migrations are typically needed for prod which are typically mysql/postgresql in croogo's case.