[4.0] Fix database error shown after new installation with PostgreSQL database #28605
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
@alikon Could you test this? Thanks in advance. |
Contributor
|
I have tested this item ✅ successfully on b6c9172 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/28605. |
Contributor
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request for Issue # .
Summary of Changes
With PR #28350 the installation sql has been restructured, i.e. joomla.sql has been split up into 3 files.
In file
supports.sqlfor PostgreSQL, the#__csptable got lost somehow.This PR adds it back.
Testing Instructions
Can be tested only with PostgreSQL. MySQL or MariaDB don't have this issue.
Install a current 4.0-dev or nightly build of last night using a PostgreSQL database.
After successful installation, login to backend and go to "System - Information - Database".
Result: See section "Actual result" below.
Apply the patch of this PR.
Remove configuration.php and make again a new installation using a PostgreSQL database.
After successful installation, login to backend and go to "System - Information - Database".
Result: See section "Expected result" below.
Expected result
Actual result
Documentation Changes Required
None.