JInstaller: :Install: Error SQL Column 'checked_out_time' cannot be null
Obviously we shouldn't get this failed SQL error. As a result pretty much the entire J4 Schema migrations fail to run so you get empty system dashboards so basically a total disaster :)
mysql --version mysql Ver 15.1 Distrib 10.3.16-MariaDB, for osx10.14 (x86_64) using readline 5.1
No Code Attached Yet
Maybe it needs the same check as done with PR #27228 for the core_checked_out_time column of the ucm content table also for the checked_out_time columns of any table where we have this, i.e. convert emptry strings to old (pseudo-) null dates in the same update sql script where we modify that column to accept real null values, just before the corresponding alter table modify statement?
Can be reproduced also with staging or 3.9.16 when using upload&update.
Same on a clean 3.10-dev branch without any sample data ... joomlaupdate log file shows as last statement:
CREATE TABLE IF NOT EXISTS #__webauthn_credentials
VARCHAR(. from file
Am investigating and will try to solve it.
The reason is the webauthn update sql script
4.0.0-2019-07-02.sql uses already
NULL for the
checked_out_time column when inserting its record into the
#__extensions table, but this column in this table is changed to allow real
NULL values in script
4.0.0-2019-10-06.sql, which runs after the previously mentioned one on update ;-)
It's the same for MySQL and PostgreSQL.
|Closed_Date||0000-00-00 00:00:00||⇒||2020-03-18 18:37:46|
Added back Beta Blocker label since it was removed when the issue was closed.
What is strange: When I've tested yesterday with MySQL 8 and PostgreSQL 11 and my PR applied, it worked. And I've just checked the update package from last nightly build: It contains the changes from my PR.
Still can't reproduce that anymore since my PR has been merged, neither with MySQL 5.7 now with MySQL 8, using the official nightly build download URL as custom URL, as described in the description of this issue.
There is another issue not related to this one here, error related to removed fields plugin, shown one time after first login to backend, but SQL all went fine. For the fields issue I'll make new issue or PR soon.
|Closed_Date||0000-00-00 00:00:00||⇒||2020-03-19 22:54:24|