Installation v. 6.19 -> v. 6.20 -> v. 7.0 was OK.

I have the error described in the issue http://drupal.org/node/952394.

But what makes more troubles, database update script doesn't work. Some newly installed modules (mainly Views Something) require database update. This requirement is displayed correctly in the Status Report. However, update.php always informs there are no available updates (see the screenshot below) and Status Report keeps informing the same requirement.

In fact, outdated database makes some errors in the site behavior.

CommentFileSizeAuthor
updates2.png8.1 KBAndrzejG
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bfroehle’s picture

Component: update.module » database update system
AndrzejG’s picture

My site lost some styles, "Cannot modify header information" (see similar http://drupal.org/node/1071270), and got "unexpected errors". After disabling some modules the errors remained related to the update.php dysfunction:

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mysite.field_deleted_data_31' doesn't exist: SELECT DISTINCT field_deleted_data_310.entity_type AS entity_type, field_deleted_data_310.entity_id AS entity_id, field_deleted_data_310.revision_id AS revision_id, field_deleted_data_310.bundle AS bundle FROM {field_deleted_data_31} field_deleted_data_310 LEFT OUTER JOIN {node_access} na ON na.nid = field_deleted_data_310.entity_id WHERE (field_deleted_data_310.deleted = :db_condition_placeholder_0) AND (field_deleted_data_310.bundle = :db_condition_placeholder_1) AND(((( (na.gid = :db_condition_placeholder_2) AND (na.realm = :db_condition_placeholder_3) ))AND (na.grant_view >= :db_condition_placeholder_4) AND (field_deleted_data_310.entity_type = :db_condition_placeholder_5) )OR (field_deleted_data_310.entity_type <> :db_condition_placeholder_6) ) LIMIT 10 OFFSET 0; Array ( [:db_condition_placeholder_0] => 1 [:db_condition_placeholder_1] => gallery_collections [:db_condition_placeholder_2] => 0 [:db_condition_placeholder_3] => all [:db_condition_placeholder_4] => 1 [:db_condition_placeholder_5] => node [:db_condition_placeholder_6] => node ) w field_sql_storage_field_storage_query() (linia 569 z /modules/field/modules/field_sql_storage/field_sql_storage.module).

Please note that there are a lot of similar errors reported,
http://drupal.org/search/apachesolr_multisitesearch/PDOException%3A%20SQ...

Please help asap!

AndrzejG’s picture

I there any interest in this issue?

Starminder’s picture

This is being discussed in a couple of other places, and some patches for update.php are there that may help your situation.

AndrzejG’s picture

Wow! Just now updated Nodequeue to nodequeue 7.x-2.0-alpha2, and database has been updated successfully!

sun’s picture

Category: bug » support
Priority: Major » Normal
Status: Active » Fixed

#5 indicates that the issue has been resolved.

AndrzejG’s picture

Category: support » bug
Status: Fixed » Needs work

No no, opposite. The situation got alarming, even critical, as I perceive.

Now hundreds of people who develop and test core and contributed modules waste their time and effort facing the need of always working on clean installations or searching for the causes of surprising errors. Most of them are not conscious of the real cause.

Only positive is that now, in Drupal 7.2, the cause seems to be clearly detected - the update process doesn't rebuild the index. Please see http://drupal.org/node/1170312#comment-4547662.

The urgent action should be taken to join efforts of core and leading Drupal developers to resolve the issue.

AndrzejG’s picture

Version: 7.0 » 7.2

Sorry, missed to change Drupal version.

bfroehle’s picture

Status: Needs work » Closed (duplicate)
AndrzejG’s picture

The link above leads to the Chaos tool suite issues. However, the comment linked indicates that the issue is found in Drupal Core.

I don't understand the game of closing tickets here but I hope Your action will be taken as soon as possible to fix this issue.

bfroehle’s picture