On update.inc line 458:

// Add the cache_path table.
require_once('./modules/system/system.install');
$schema['cache_path'] = system_schema_cache_7054();
$schema['cache_path']['description'] = 'Cache table used for path alias lookups.';
db_create_table('cache_path', $schema['cache_path']);

This fails on Pressflow sites with path_alias_cache module enabled, since the cache_path table will already exist in the database. You can argue that since Pressflow is a fork of Drupal, but this would fail on normal Drupal sites if they happened to have created such a table with that name.

Since it's a cache table a possible solution could be to add.

DROP TABLE IF EXISTS

CommentFileSizeAuthor
#3 934634-cache-path-pressflow.patch755 bytescarlos8f
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

webchick’s picture

Issue tags: +D7 upgrade path

Tagging.

In general, I'm against Drupal doing backflips to accommodate forks (well, "spoons" ;)). In this case it seems like a fairly easy change to make, but let's see what folks say.

webchick’s picture

Component: other » update system
carlos8f’s picture

Status: Active » Needs review
FileSize
755 bytes

This problem has been bugging me since I am testing the upgrade path using a real site which runs Pressflow. I have to remember to drop the cache_path table every time. If I don't, update_fix_d7_requirements() doesn't finish, and cannot be re-run either. Have to start all over XD

Tested the patch and ran a successful upgrade without having to drop cache_path manually.

Status: Needs review » Needs work
Issue tags: -D7 upgrade path

The last submitted patch, 934634-cache-path-pressflow.patch, failed testing.

carlos8f’s picture

Status: Needs work » Needs review

#3: 934634-cache-path-pressflow.patch queued for re-testing.

sun’s picture

Issue tags: +D7 upgrade path

#3: 934634-cache-path-pressflow.patch queued for re-testing.

sun’s picture

Status: Needs review » Reviewed & tested by the community

RTBC if bot passes.

webchick’s picture

Status: Reviewed & tested by the community » Fixed

I looked through the rest of system.install and confirmed that we generally do check if the table is there first before creating new ones. So this seems pretty consistent, regardless of what is ultimately causing that table to show up twice.

Committed to HEAD.

Status: Fixed » Closed (fixed)
Issue tags: -D7 upgrade path

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