Difference between revisions of "Database Errors When Upgrading to 2.5.0"
From Joomla! Documentation
Betweenbrain (talk | contribs) (Created page with "When upgrading from an earlier, compatible version, to 2.5.0, you may experience a database error such as the following <code>JInstaller: :Install: Error SQL DB function failed ...") |
m (clean up categories with <noinclude> tags) |
||
| Line 12: | Line 12: | ||
To fix this issues, go to Extension Manager -> Database then click the fix button. This will attempt to fix any database issues caused by changes in the database structure that occurred between versions. | To fix this issues, go to Extension Manager -> Database then click the fix button. This will attempt to fix any database issues caused by changes in the database structure that occurred between versions. | ||
| − | [[Category:Version 2.5 FAQ]][[Category:Version 2.5.0 FAQ]] | + | <noinclude>[[Category:Version 2.5 FAQ]][[Category:Version 2.5.0 FAQ]]</noinclude> |
Revision as of 17:09, 1 September 2012
The "J2.5" namespace is a namespace scheduled to be archived. This page contains information for a Joomla! version which is no longer supported. It exists only as a historical reference, it will not be improved and its content may be incomplete and/or contain broken links.
When upgrading from an earlier, compatible version, to 2.5.0, you may experience a database error such as the following
JInstaller: :Install: Error SQL DB function failed with error number 1060
Duplicate column name 'ordering' SQL=ALTER TABLE `j17_languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
SQL =
ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
Files Update: SQL error file DB function failed with error number 1060
Duplicate column name 'ordering' SQL=ALTER TABLE `j17_languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
SQL =
ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;"
To fix this issues, go to Extension Manager -> Database then click the fix button. This will attempt to fix any database issues caused by changes in the database structure that occurred between versions.