User tests: Successful: Unsuccessful:
As described in #4922 and #5177 the posgresql database schema is not up to date after installation. Apply this patch before installing. Then install on a postgresql database with "Install Sample Data" set to None. Login in the backend and go to the "Extension Manager" -> "Database" and verify that the database schema is uptodate.
Labels |
Added:
?
|
Rel_Number | ⇒ | 5177 | |
Relation Type | ⇒ | Related to |
Category | ⇒ | Postgresql |
@test success
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5186.
Two good tests setting to RTC
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5186.
Status | Pending | ⇒ | Ready to Commit |
Labels |
Added:
?
|
@waader You can't do it this way with the update SQL files.
Those will only have an effect for people updating from 3.2.1 and 3.3.3 respectively. If you want to fix it for all updating users, you need to create a new file 3.4.0-2014-12-03.sql
where you fix the schema.
Can you update the PR and add the SQL into this new file?
@bakual I played around with the update mechanism and from my expierences I have to do it that way otherwise you will always have entries like "Table 'd9pth_user_profiles' does not have column 'profile_value' with type TEXT" on the database tab even when I would have this new file.
But what I should do additionally is creating that new file. it would be easier for me - at the moment - if you could merge this and I would provide an additional patch.
Status | Ready to Commit | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-01-27 22:24:21 |
I made an update file with this two line:
CREATE INDEX "#__contentitem_tag_map_idx_tag_name" ON "#__contentitem_tag_map" ("tag_id", "type_alias");
ALTER TABLE "#__associations" ALTER COLUMN "id" TYPE int;
But before I applied that file I took an old joomla installation 3.1.1. and updated it to 3.2.7. From there I updated to 3.4.0-beta3 and looked up the database schema. Too my surprise the index was present and the column was of type integer. All without applying my update file. When I go to the extension manager -> database I get the message "Database table structure is up to date".
Maybe there where changes in later version but then my update file could cause problems with versions prior to that changes.
So I donĀ“t know what there should be done.
Labels |
Removed:
?
|
Works for me with both test and no sample data
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5186.