[#13122] - index 'idx_image' from file 3.7.0-2016-11-21.sql
- Closed
- 8 Dec 2016
- Medium
- Build: staging
- # 13122
Steps to reproduce the issue
Install from joomla-cms rev 2a375e3
Expected result
Database is up to date
Actual result
Table 'havxz_languages' should not have index 'idx_image'. (From file 3.7.0-2016-11-21.sql.)
Click Fix button
Table 'havxz_languages' does not have index 'idx_image'. (From file 3.7.0-2016-11-21.sql.)
Click Fix button
Table 'havxz_languages' should not have index 'idx_image'. (From file 3.7.0-2016-11-21.sql.)
Click Fix button
Table 'havxz_languages' does not have index 'idx_image'. (From file 3.7.0-2016-11-21.sql.)
Click Fix button
Table 'havxz_languages' should not have index 'idx_image'. (From file 3.7.0-2016-11-21.sql.)
System information (as much as possible)
joomla-cms-bot
- | Labels |
Added:
?
|
||
Hum it seems the database schema checker does not take into account that a new index with the same name is created after.
this can be resolved if we change the new index name to, for instance, #__language_image.
ALTER TABLE `#__languages` DROP INDEX `idx_image`;
ALTER TABLE `#__languages` ADD INDEX `idx_language_image` (`image`);But maybe there is another way, but i'm no db expert.
it would be nice to have @alikon option on this.
The DROP INDEX and ADD INDEX need to be in the same statement.
Yes, but how we do that in the 3 db system? Suggestions?
brianteeman
- | Status | New | ⇒ | Confirmed |
@andrepereiradasilva can you test adding a COMMIT; between the 2 ALTER statments ?
tested. doesn't work also.
ALTER TABLE #__languages DROP INDEX idx_image , ADD INDEX idx_image ;
Replace INDEX with CONSTRAINT for PG and MS SQL.
Obviously the names are different and these subcommands aren't recognized by schema checker.
They shouldn't cause the problems mentionedhere.
| Status | Confirmed | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-12-08 14:14:36 |
| Closed_By | ⇒ | Bakual |
Closing as we have a PR.
Might be related to #12949