4.7 to 5.x upgrade problem : cache_content error after update.php

I'm not able to look precisely into the code, but I guess this is because of API calls in the update functions that get executed before the one that creates the content_cache table.

That is a typical yet easy to miss issue with updates (specifically CCK updates, where updates can be quite complex and often use CCK API calls, which in turn make some asumptions on the state of the db which might not be true -yet- when running an update). Not really easy to fix, too, because we can't just change the order of update functions.

Core updates solve this by hardcoding some preliminary update operations in update.php (typically, creation of cache tables...) - not sure how this could be adapted to contrib modules.
Adding something like if (!db_table_exists('cache_content')) { ... create the table ...} at the top-level of content.install ?

This is actually not _that_ important. Those errors should not have any real consequence and the upgrade should be fine in the end, but of course it would be best not to get any error to begin with...

Should be fixed in latest 5.x-1.x-dev release (and forthcoming 5.x-1.6 release)

@meles : you don't seem to follow the right steps for the update. If a module is disabled when you run update.php, it's updates won't get executed.

You should be doing the following :
- Do _not_ disable CCK modules
- remove the old cck folder from the modules directory, replace with the new one.
- run update.php

And thus, switching back to the original title, for archiving sake.

Just a really late followup for anyone else updating an old Drupal 5 site. I'm updating one (that I haven't been the admin for) from 5.1 to 5.19 and just ran into this same issue. You can create the cache_content and cache_views tables via phpMyAdmin prior to running update.php to avoid the errors. Here is the code:

CREATE TABLE cache_content (
        cid varchar(255) NOT NULL default '',
        data longblob,
        expire int NOT NULL default '0',
        created int NOT NULL default '0',
        headers text,
        PRIMARY KEY (cid),
        INDEX expire (expire)
      )

CREATE TABLE cache_views (
        cid varchar(255) NOT NULL default '',
        data longblob,
        expire int NOT NULL default '0',
        created int NOT NULL default '0',
        headers text,
        PRIMARY KEY (cid),
        INDEX expire (expire)
      )

Hope this helps!

I'm upgrading a site from 4.7 through 5.2 on its way to 6.14. Just a note that adding your two tables to the 4.7 database enabled the CCK modules to update correctly in 5.2. And for those not familiar with SQL, note that you want to run each command separately in PHPMyAdmin with a semicolon after it. Thanks!

I use Drupal 6.22 and drigg-6.x-1.x-dev. if create content page and story no have problem, but if after create scoop get error "user warning: Table 'admin567.cache_content' doesn't exist query: DELETE FROM cache_content WHERE cid = 'content:39:39' in /home/admin/domain/includes/cache.inc on line 178"

how to fix it ??