Feeling Lucky
J4 Issue
?
[#24769] - [4.0] [PostgreSQL] Database problem with com_finder tables after new installation
- Closed
- 1 May 2019
- Medium
- Build: 4.0-dev
- # 24769
Steps to reproduce the issue
- Pull current (May 1, 2019) 4.0-dev branch and do
composer installandnpm ci, or use nightly build from tonight. Both include PR #24747, which is needed to install on PostgreSQL. Alpha 8 does not include that yet, so please don't use Alpha 8. - Install Joomla 4 using a PostgreSQL database.
- After installation has finished with success, login to backend, confirm the statistics dialog, then goto the system panel and check section "Information - Database". Result: You see that there is 1 database problem.
- Click "Database" to get to the Database view.
Expected result
No database problems.
Actual result
System information (as much as possible)
Current 4.0-dev branch (today is May 1, 2019) fresh installation using PostgreSQL database.
Additional comments
The problem came up after PR #20561 was merged.
joomla-cms-bot
- 
franz-wohlkoenig
- | Labels |
Added:
J4 Issue
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-05-01 11:09:11 |
| Closed_By | ⇒ | richard67 |
@alikon Because you test with PostgreSQL, too: Can you reproduce this issue?
@Hackwar It seems that in your PR #20561 , the changes in joomla.sql and 4.0.0-2018-07-29.sql for postgresql database are not consistent, because the database checker checks the schema updates. Maybe you can check and fix?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24769.