I just got this issue when trying to clear the cache here http://drupal7.dev.openconcept.ca/admin/config/development/performance

It then ended with a nasty error:

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'hash' in 'field list': UPDATE {registry_file} SET hash=:db_update_placeholder_0 WHERE (filename = :db_condition_placeholder_0) ; Array ( [:db_update_placeholder_0] => b555ab7000c56fcfbc5251e6b40a5652a13a6bc2efe86708b26162b633c47a33 [:db_condition_placeholder_0] => modules/aggregator/aggregator.module )  in _registry_parse_files() (line 150 of /drupal/includes/registry.inc).

Comments

Anonymous’s picture

we recently switched back to using file hashes rather than file modification times for the registry: #819388: Switch registry back to using hashes not file mtime and ctime.

weboide’s picture

I just had the same error with HEAD.

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'hash' in 'field list': UPDATE {registry_file} SET hash=:db_update_placeholder_0 WHERE (filename = :db_condition_placeholder_0) ; Array ( [:db_update_placeholder_0] => 25dae6eb89e663c22908452c841522f38057fec731b7061c7496babd09cd3dbd [:db_condition_placeholder_0] => modules/block/block.module ) in _registry_parse_files() (line 150 of /home/drupalconcept/www/drupal/includes/registry.inc).

damien tournoud’s picture

Status: Active » Closed (won't fix)

Yep, we changed the schema. You will have to reinstall from scratch.

mgifford’s picture

When are we going to have it so that there needs to be an upgrade patch or something so that we don't have to keep upgrading from scratch all the time.

It really slows down things when I have to start up a new environment every other week.

It doesn't have to be fancy, just something like "run this SQL on your system" and you're good to go.

damien tournoud’s picture

@mgifford: see the HEAD2HEAD project.

Core itself will support incremental upgrades when we will reach the first beta version.

mgifford’s picture

very useful, thanks!

klonos’s picture

subscribing... in case it is fixed someday.

klonos’s picture

Do schema changes actually mean that re-installing is the only path to get out of such trouble, or is there some other way? Please share any insight.

nargis’s picture

Assigned: Unassigned » nargis

help me please, I 've got same issue

klonos’s picture

Assigned: nargis » Unassigned

Hi Rusydi, please onl assign issue to yourself if you intent to code for it and provide a solution.

Although no one has answered my question in #8 yet, I believe that I can safelly say that reinstalliing is the only way to go (as Damien says in #3). I am sorry.

nargis’s picture

ok, thanks!

eee.coop’s picture

How can I transfer the content across to the new installation?