SQL Syntax error or access violation updating Horde_History DB schema

Trying to update the Horde_History database schema after pea

Thu, 25 Jul 2013 00:31:34 +0000

Trying to update the Horde_History database schema after pear package update, the configuration page displays that the DB schema as outdated for Horde_History but displays the following message when trying to update its schema: SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'index_horde_histories_on_history_modseq'; check that column/key exists Horde database created by H4 about a year ago, reused by H5.1.1 now.

My guess is that because of the confusion we created surroun

Thu, 25 Jul 2013 03:19:07 +0000

My guess is that because of the confusion we created surrounding the upgrade of the History package you ran the migration before the final correct fix was in place. The migration might have succeeded enough to remove the index but no update the schema version. Try migrating to version 4 and then back up to 6. If that fails, you can edit the migration files and comment out the $this->removeIndex() line in the 6 migration.

> My guess is that because of the confusion we created surro

Fri, 26 Jul 2013 10:38:27 +0000

> My guess is that because of the confusion we created surrounding the > upgrade of the History package you ran the migration before the final > correct fix was in place. The migration might have succeeded enough > to remove the index but no update the schema version. > > Try migrating to version 4 and then back up to 6. If that fails, you > can edit the migration files and comment out the $this->removeIndex() > line in the 6 migration. Wher can i find the migration files? With the today update of Horde_History from 2.1.1 to 2.1.5 we have the very same error. Or can i simply create a index with this name and let the schema upgrade remove it?

>> My guess is that because of the confusion we created surr

Fri, 26 Jul 2013 13:23:52 +0000

>> My guess is that because of the confusion we created surrounding the >> upgrade of the History package you ran the migration before the final >> correct fix was in place. The migration might have succeeded enough >> to remove the index but no update the schema version. >> >> Try migrating to version 4 and then back up to 6. If that fails, you >> can edit the migration files and comment out the $this->removeIndex() >> line in the 6 migration. > > Wher can i find the migration files? With the today update of > Horde_History from 2.1.1 to 2.1.5 we have the very same error. > Or can i simply create a index with this name and let the schema > upgrade remove it? Sure, that's another (probably simpler) way to go.

> Wher can i find the migration files? With the today update

Fri, 26 Jul 2013 14:48:39 +0000

> Wher can i find the migration files? With the today update of > Horde_History from 2.1.1 to 2.1.5 we have the very same error. > Or can i simply create a index with this name and let the schema > upgrade remove it? Same problem here: Migrating to HordeHistoryRemoveCompositeIndex (5) == 5 HordeHistoryRemoveCompositeIndex: migrating ============================== -- removeIndex('horde_histories', 'history_modseq') QUERY FAILED: Can't DROP 'index_horde_histories_on_history_modseq'; check that column/key exists DROP INDEX `index_horde_histories_on_history_modseq` ON `horde_histories`

Is my database structure ok? Can someone give me the right

Fri, 26 Jul 2013 15:36:23 +0000

Is my database structure ok? Can someone give me the right sql command to fix the upgrade? -- -- Tabellenstruktur für Tabelle `horde_histories` -- CREATE TABLE IF NOT EXISTS `horde_histories` ( `history_id` int(10) unsigned NOT NULL AUTO_INCREMENT, `object_uid` varchar(255) NOT NULL, `history_action` varchar(32) NOT NULL, `history_ts` int(11) NOT NULL, `history_desc` longtext, `history_who` varchar(255) DEFAULT NULL, `history_extra` longtext, `history_modseq` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`history_id`), KEY `history_action_idx` (`history_action`), KEY `history_ts_idx` (`history_ts`), KEY `history_uid_idx` (`object_uid`), KEY `index_horde_histories_on_history_modseq_and_object_uid` (`history_modseq`,`object_uid`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=74754 ;

I'm beginning to think that the way indexes are named has ch

Fri, 26 Jul 2013 16:38:59 +0000

I'm beginning to think that the way indexes are named has changed at some point in the past so that when we generate the name of the index to drop, it doesn't match the name it was created with in the past. We probably need to catch the error and try to remove the old name explicitly when this happens.

> I'm beginning to think that the way indexes are named has

Fri, 26 Jul 2013 20:20:19 +0000

> I'm beginning to think that the way indexes are named has changed at > some point in the past so that when we generate the name of the index > to drop, it doesn't match the name it was created with in the past. > > We probably need to catch the error and try to remove the old name > explicitly when this happens. OK so I am not a MySQL Guru, can someone recommend a MySQL command to try to fix this?

> OK so I am not a MySQL Guru, can someone recommend a MySQL

Sat, 27 Jul 2013 07:41:13 +0000

> OK so I am not a MySQL Guru, can someone recommend a MySQL command to > try to fix this? I fixed it with the following steps: * horde-db-migrate show Horde_History schema version: 4 and the SQL error. * comment out the up function in the following files (/usr/share/php/data/Horde_History/migration): 5_horde_history_remove_compositeindex.php 6_horde_history_fix_botchedindexes.php * run horde-db-migrate to update to Horde_History schema version: 6 * I use phpmyadmin to delete all indexes in the horde_histories table except the "PRIMARY key * at last add the indexes with the following commands ALTER TABLE `HORDE_DB_NAME`.`horde_histories` ADD INDEX `index_horde_histories_on_history_action` ( `history_action` ) ALTER TABLE `HORDE_DB_NAME`.`horde_histories` ADD INDEX `index_horde_histories_on_history_ts` ( `history_ts` ) ALTER TABLE `HORDE_DB_NAME`.`horde_histories` ADD INDEX `index_horde_histories_on_history_modseq` ( `history_modseq` ) ALTER TABLE `HORDE_DB_NAME`.`horde_histories` ADD INDEX `index_horde_histories_on_object_uid` ( `object_uid` ) I hope this helps.

>> OK so I am not a MySQL Guru, can someone recommend a MySQ

Sat, 27 Jul 2013 14:38:34 +0000

>> OK so I am not a MySQL Guru, can someone recommend a MySQL command to >> try to fix this? > > I fixed it with the following steps: > * horde-db-migrate show Horde_History schema version: 4 and the SQL error. > * comment out the up function in the following files > (/usr/share/php/data/Horde_History/migration): > 5_horde_history_remove_compositeindex.php > 6_horde_history_fix_botchedindexes.php > * run horde-db-migrate to update to Horde_History schema version: 6 > * I use phpmyadmin to delete all indexes in the horde_histories table > except the "PRIMARY key > * at last add the indexes with the following commands > ALTER TABLE `HORDE_DB_NAME`.`horde_histories` ADD INDEX > `index_horde_histories_on_history_action` ( `history_action` ) > ALTER TABLE `HORDE_DB_NAME`.`horde_histories` ADD INDEX > `index_horde_histories_on_history_ts` ( `history_ts` ) > ALTER TABLE `HORDE_DB_NAME`.`horde_histories` ADD INDEX > `index_horde_histories_on_history_modseq` ( `history_modseq` ) > ALTER TABLE `HORDE_DB_NAME`.`horde_histories` ADD INDEX > `index_horde_histories_on_object_uid` ( `object_uid` ) > > I hope this helps. > OK Half of your procedure worked, the SQL part didnt. I am not sure exactly how to execute these SQL commands .. I tried in phpmyadmin, going into the horde_db then navigting in horde_histories table then clicking on the SQL (Run SQL Query) and copy paste the commands you provided, I get #1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ALTER TABLE `hordedb`.`horde_histories` ADD INDEX `index_horde_histories_on_hist' at line 2 I tried one by one thinking SQL didnt like the back-to-back with multiple commands in the same query (I know it can do many commands in one query but...) and I got: #1072 - Key column 'history_ts' doesn't exist in table Not sure how to push these commands in SQL. Can you help ? Very aprpeciated!

> I am not sure exactly how to execute these SQL commands ..

Sat, 27 Jul 2013 14:50:19 +0000

> I am not sure exactly how to execute these SQL commands .. I tried > in phpmyadmin, going into the horde_db then navigting in > horde_histories table then clicking on the SQL (Run SQL Query) and > copy paste the commands you provided, I get Where are all your columns gone?

>> I am not sure exactly how to execute these SQL commands .

Sat, 27 Jul 2013 16:57:07 +0000

>> I am not sure exactly how to execute these SQL commands .. I tried >> in phpmyadmin, going into the horde_db then navigting in >> horde_histories table then clicking on the SQL (Run SQL Query) and >> copy paste the commands you provided, I get > > Where are all your columns gone? Deleted I guess... When you said "I use phpmyadmin to delete all indexes in the horde_histories table except the "PRIMARY key" this is what I did, I deleted all columns except the primary key. I guess I confused indexes and columns... Can I just recreate the columns and then run your commands? I am afraid to keep screwing around with that, since I dont know what Im doing...

> Deleted I guess... In this case you need the backup of

Sat, 27 Jul 2013 19:06:14 +0000

> Deleted I guess... In this case you need the backup of your database. > When you said "I use phpmyadmin to delete all indexes in the horde_histories > table except the "PRIMARY key" this is what I did, I deleted all > columns except the primary key. Yes I said delete indexes *not* columns. I do not know what is to do now.

Changes have been made in Git (master): commit 0e4a486e140a

Fri, 02 Aug 2013 21:03:54 +0000

Changes have been made in Git (master): commit 0e4a486e140a43a63adc9b9357b0f0c0a7d80283 Author: Michael J Rubinsky Date: Fri Aug 2 17:02:31 2013 -0400 Only remove index if we have the current index name. Bug: 12498 .../History/4_horde_history_add_compositeindex.php | 14 +++++++++++- .../5_horde_history_remove_compositeindex.php | 14 +++++++++++- .../History/6_horde_history_fix_botchedindexes.php | 21 +++++++++++++++++-- 3 files changed, 42 insertions(+), 7 deletions(-) http://git.horde.org/horde-git/-/commit/0e4a486e140a43a63adc9b9357b0f0c0a7d80283

Hopefully the last of the issues surrounding the latest Hist

Fri, 02 Aug 2013 21:07:04 +0000

Hopefully the last of the issues surrounding the latest History updates.

> Is my database structure ok? > Can someone give me the ri

Sat, 30 Dec 2023 21:37:01 +0000

> Is my database structure ok? > Can someone give me the right sql command to fix the upgrade? > > -- > -- Tabellenstruktur für Tabelle `horde_histories` > -- > > CREATE TABLE IF NOT EXISTS `horde_histories` ( > `history_id` int(10) unsigned NOT NULL AUTO_INCREMENT, > `object_uid` varchar(255) NOT NULL, > `history_action` varchar(32) NOT NULL, > `history_ts` int(11) NOT NULL, > `history_desc` longtext, > `history_who` varchar(255) DEFAULT NULL, > `history_extra` longtext, > `history_modseq` int(11) NOT NULL DEFAULT '0', > PRIMARY KEY (`history_id`), > KEY `history_action_idx` (`history_action`), > KEY `history_ts_idx` (`history_ts`), > KEY `history_uid_idx` (`object_uid`), > KEY `index_horde_histories_on_history_modseq_and_object_uid` > (`history_modseq`,`object_uid`) > ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=74754 ;

>> Is my database structure ok? >> Can someone give me the

Tue, 02 Jan 2024 12:50:44 +0000

>> Is my database structure ok? >> Can someone give me the right sql command to fix the upgrade? Moin! I use this: /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `horde_histories` ( `history_id` int(10) unsigned NOT NULL AUTO_INCREMENT, `object_uid` varchar(255) NOT NULL, `history_action` varchar(32) NOT NULL, `history_ts` bigint(20) NOT NULL, `history_desc` text DEFAULT NULL, `history_who` varchar(255) DEFAULT NULL, `history_extra` text DEFAULT NULL, `history_modseq` int(11) NOT NULL DEFAULT 0, PRIMARY KEY (`history_id`), KEY `history_action_idx` (`history_action`), KEY `history_ts_idx` (`history_ts`), KEY `history_uid_idx` (`object_uid`), KEY `index_horde_histories_on_history_modseq` (`history_modseq`), KEY `index_horde_histories_on_object_uid` (`object_uid`), KEY `history_modseq_idx` (`history_modseq`) ) ENGINE=MyISAM AUTO_INCREMENT=14715533 DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; :-) Arnold