filter_update_7002() renames the filter tables. however, since the work of drupal_get_schema() is cached, future updates that run into that function bomb. this patch fixes things by simply resetting the cache after the table renames. this fixes breakage in filter_update_7005().

CommentFileSizeAuthor
filter_update_fix.patch652 byteshunmonk

Comments

webchick’s picture

Status: Needs review » Needs work

Seems like db_rename_table() ought to be doing this for you, no?

damien tournoud’s picture

The schema from drupal_get_schema() is the *theoretical* schema, ie. what's defined in hook_schema(). It has nothing to do with what's inside the database. On the other hand, db_*() functions only touch the database, not the theoretical schema.

If there is an issue here, it's probably not related to the schema being cached.

hunmonk’s picture

Status: Needs work » Fixed

right, i certainly was thinking of it incorrectly.

i'm not sure why my fix made a difference then -- at any rate, with the latest patch over at #211182: Updates run in unpredictable order i don't have this issue anymore.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.