Update function refers to the database table as {{votingapi_vote}}

I cannot confirm the FAIL with mysql 5.0, but the bug.

Fixed in the dev snapshot. Thanks!

* user warning: Table 'drupal_drupal_votingapi_vote' doesn't exist query: ALTER TABLE drupal_drupal_votingapi_vote DROP INDEX
* user warning: Table 'drupal_drupal_votingapi_vote' doesn't exist query: ALTER TABLE drupal_drupal_votingapi_vote DROP INDEX

    * user warning: Table 'db1141249-drupal6.drupaldrupalvotingapi_vote' doesn't exist query: ALTER TABLE drupaldrupalvotingapi_vote DROP INDEX content in /is/htdocs/wp1141249_Q7UT4FKE6D/www/drupal6/includes/database.mysql-common.inc on line 448.
    * user warning: Table 'db1141249-drupal6.drupaldrupalvotingapi_vote' doesn't exist query: ALTER TABLE drupaldrupalvotingapi_vote DROP INDEX content_vtype in /is/htdocs/wp1141249_Q7UT4FKE6D/www/drupal6/includes/database.mysql-common.inc on line 448.

is the same issue I guess?

Anything I need to do about it? Can it be ignored, or what?

Yeah, this is all the same... I have no table prefix and this may be the reason why I haven't seen the fails.

You both need to run the ALTER operations manually as eaton haven't added an update hook to DEV, yet.

Hmm? "run ALTER operations manually" would be done how? I have to admit that I have no clue about it.

Or should I wait for the next dev?

Thanks in advance for any guidance on this.

@dddave: Execute this on your mysql server

ALTER TABLE drupalvotingapi_vote DROP INDEX content
ALTER TABLE drupalvotingapi_vote DROP INDEX content_vtype

I guess this means entering it into the field that opens when I click on the sql tab in phpmyadmin?

Can I do them both in one shot or one after the other?

Thanks for the handholding. This is the first time I am doing something like this and off course I didn't back up the database (as I normally do) or checked the issue queue in advance (as I normally do). This bites my now.
I would have tried it on my local install but the update ran without problems there.

@eaton: Please add an update hook... :-)

An additional update hook has been added that re-does the work of the 6101 update, but without the typo.

Please note that the broken update doesn't hurt anything -- your site will continue to work fine, and all data will still be stored properly. The update in question was just creating a couple of specific indexes so that sites with large numbers of votes could retrieve them faster.

Thanks!