I was able to upgrade from beta 1, 2 and 3 just fine but with the same database I am now unable to upgrade to rc1. On my initial update.php run I get the following error:

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mostrey.main_system' doesn't exist: SELECT name, schema_version FROM {system} WHERE type = :type; Array ( [:type] => module ) in drupal_get_installed_schema_version() (line 151 of /Applications/MAMP/mostrey/includes/install.inc).

It's obvious the main_system table doesn't exist yet, that's why I'm running update.php in the first place.

Comments

int’s picture

int commented
Version: 7.0-rc1 » 7.x-dev
Priority: Major » Critical

If you can update Drupal 6 to Drupal 7 B1/B2/B3, but you can't update Drupal 6 to Drupal 7 RC1 it's a regression.
This bug is critical.

Change to dev for this

carlos8f’s picture

carlos8f commented

subscribing

Stevel’s picture

Stevel commented

The system table exists in drupal 6 as well. I assume main_ is the prefix you are using? Not sure what is going on here yet. Can you give some more information regarding your setup?

Stevel’s picture

Stevel commented
Issue tags: +D7 upgrade path

and tagging

bfroehle’s picture

bfroehle commented
Issue tags: -D7 upgrade path

This some sort of table prefix error. I'm curious what $databases is set to in settings.php & default.settings.php. Are table prefixes being used in the database or not?

bfroehle’s picture

bfroehle commented
Issue tags: +D7 upgrade path

x-post

wmostrey’s picture

wmostrey commented
Category: bug » support
Priority: Critical » Normal
Status: Active » Fixed

You are correct, it was a prefix issue. During this new migration I malconfigured settings.php. All is good now.

Status: Fixed » Closed (fixed)

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

mcfilms’s picture

mcfilms commented

This is a related issue -- For my own information, you cannot go back to Drupal 7.0-rc2 once you have updated to the latest Drupal 7.x-dev? If so, I guess I'm hosed.

icecreamyou’s picture

icecreamyou commented

For the record, I had this issue while upgrading a site using Acquia Dev Desktop for D7. I had imported a D6 sql dump that used database prefixes and it was working fine on D6. After replacing the files with D7 and navigating to update.php I got this error. The reason is because Dev Desktop adds a $database array to all settings.php files at the bottom, which overrides database settings at the usual location. However, this didn't interfere with D6 because D6 uses $db_url and $db_prefix. Once I added my prefix to the $database array that Dev Desktop had generated, the error disappeared. It's possible that Dev Desktop actually has problems importing prefixed databases for Drupal 7 -- I haven't tested that. Anyway, pretty edge-case, and easily resolved if you know the cause.