I don't think this is a duplicate of http://drupal.org/node/765236 after reading through the entire thread.

I made the update after many releases, so maybe this is something that would not happen in the future, but wanted to note in case others had the problem - it can be fixed in MYSQL direct and it doesn't seem to cause a problem.

Using the latest D7, when I updated, I got the following:

Update #6008:
Failed: DatabaseSchemaObjectDoesNotExistException: Cannot change the definition of field .views_display: field doesn't exist. in DatabaseSchema_mysql->changeField() (line 435 of /home/jalann6/public_html/d7test/includes/database/mysql/schema.inc

Appears maybe that field never existed in the original views that I downloaded, entry may have been added, then later changed, leaving this a problem that will resolve itself?

Comments

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Postponed (maintainer needs more info)

You did a update from a d6 to a d7 version of views?

It would be cool if you could describe what you did

davidburns’s picture

davidburns
he/him
Primary language English
Location Philadelphia
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Issues that are postponed (maintainer needs more info) for more than 30 days without receiving an answer may be moved to closed (won't fix) or closed(unable to reproduce)as appropriate due to lack of submitter response.

Additionally, many issues get marked needs work and postponed and then sit there because nobody ever sees them again. Generally these can either be closed or reactivated, depending on whether or not they should get someone's attention