[#28391] - [4.0] Fix SQL error "Column 'checked_out_time' cannot be null" when updating the CMS
- Fixed in Code Base
- 18 Mar 2020
- Medium
- Build: 4.0-dev
- # 28391
- Diff
- richard67:4.0-dev-fix-sql-error-on-update-1
- Pending Hound Hound is busy sniffing around... Details
User tests: Successful: Unsuccessful:
Pull Request for Issue #28385 .
Summary of Changes
Use old pseudo null date in update script 4.0.0-2019-07-02.sql for checked out time, because the real null date value change is done with script 4.0.0-2019-10-06.sql, which runs after the previously mentioned one.
Testing Instructions
Has to be tested with MySQL (or MariaDB) and PostgreSQL.
Testers please report back which of these database types you have tested.
- Install a fresh copy of 3.10 nightly or a git clone of the current 3.10-dev branch (it doesn't matter if with or without any testing sample data).
- Go to the Joomla Update Component component config and set the URL to following custom URL: https://test5.richard-fath.de/next_major_list_pr-28391.xml, and the status to "development".
- Update to Joomla 4.0.
- When the update has finished, log in to backend.
Expected result
Update succeeds (except of the missing template message at the first login to the backend, which is normal).
Actual result
Update fails with SQL error "Column 'checked_out_time' cannot be null", and the CMS is broken, see issue #28385 .
Additional information
The diff clearly shows a difference between the update script for MySQL and the one for PostgreSQL in the ordering value for the inserted record.
For fixing such differences I am already on the way to prepare a PR, but it might be weekend until it will be ready.
Documentation Changes Required
None.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | SQL Administration com_admin Postgresql |
| Title |
|
||||||
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-03-18 18:39:33 |
| Closed_By | ⇒ | wilsonge | |
| Labels |
Added:
?
|
||
Thanks, too.
Thanks! Nice work!