array_keys() expects parameter 1 to be array, null given             [warning]
common.inc:6969
WD php: PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown[error]
column 'bean.vid' in 'field list': SELECT bean.bid AS entity_id,
bean.vid AS revision_id, bean.type AS bundle, :entity_type AS
entity_type
FROM
{bean} bean; Array
(
    [:entity_type] => bean
)
in EntityFieldQuery->execute() (line 1145 of
SITEPATH/includes/entity.inc).
Drush command terminated abnormally due to an unrecoverable error.   [error]
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'bean.vid' in 'field list': SELECT bean.bid AS entity_id, bean.vid AS revision_id, bean.type AS bundle, :entity_type AS entity_type
FROM
{bean} bean; Array
(
    [:entity_type] => bean
)
in EntityFieldQuery->execute() (line 1145 of SITEPATH/includes/entity.inc).Backups were restored successfully.                                  [ok]

Just changed to SITEPATH to hide where it is.

Any ideas what's going wrong?

Comments

brantwynn’s picture

Ran into this same problem today. Switched to dev branch and did update.php manually. It threw some errors but the revisions table was created and everything seems ok...

Here's the dump of errors I saw running update.php

Warning: array_keys() [function.array-keys]: The first argument should be an array in drupal_schema_fields_sql() (line 6969 of /var/www/sites/gc011.prometdev.com/includes/common.inc).
Warning: array_keys() [function.array-keys]: The first argument should be an array in drupal_schema_fields_sql() (line 6969 of /var/www/sites/gc011.prometdev.com/includes/common.inc).
Warning: array_keys() [function.array-keys]: The first argument should be an array in drupal_schema_fields_sql() (line 6969 of /var/www/sites/gc011.prometdev.com/includes/common.inc).
Warning: array_keys() [function.array-keys]: The first argument should be an array in drupal_schema_fields_sql() (line 6969 of /var/www/sites/gc011.prometdev.com/includes/common.inc).
Warning: array_keys() [function.array-keys]: The first argument should be an array in drupal_schema_fields_sql() (line 6969 of /var/www/sites/gc011.prometdev.com/includes/common.inc).
Warning: array_keys() [function.array-keys]: The first argument should be an array in drupal_schema_fields_sql() (line 6969 of /var/www/sites/gc011.prometdev.com/includes/common.inc).
Warning: array_keys() [function.array-keys]: The first argument should be an array in drupal_schema_fields_sql() (line 6969 of /var/www/sites/gc011.prometdev.com/includes/common.inc).
pbz1912’s picture

There didn't seem to be any issues updating with the module through the admin/modules/update page. Odd.

enzipher’s picture

Ran into this as well. Running drush updatedb takes care of it.

Cheers,

Elijah Lynn’s picture

Same here, something is happening with the latest hook_update_N().

function bean_update_7007(&$return) {
  $t = get_t();
  drupal_load('module', 'bean');
  cache_clear_all('schema', 'cache'); // So we actually load the current schema.
  $schema = bean_schema();
  $bean = $schema['bean'];
  $bean_revision = $schema['bean_revision'];

I ran into something like this the other day, using drupal_flush_all_caches() instead of cache_clear_all() did the trick and the update ran on install. This should help troubleshoot the issue further since running drush updb as mentioned above does install the update, but it should have installed the update on install/update.

metzlerd’s picture

Priority:Normal» Critical

Also ran into this problem, drush upgrade appears to be non-functional. Were it my module, I'd think this would be a release blocker, so am upping priority? I don't see a work around without abandoning drush for the upgrade. Anyone else have one?

indytechcook’s picture

indytechcook’s picture

I"m tagging a new release then I'll test this. I "hope" it's fixed.

indytechcook’s picture

Status:Active» Fixed

I am able to use drush to update now with RC10.

pearlbear’s picture

I wasn't able to upgrade to either rc10 or 1.0. Both give the same error above.

Status:Fixed» Closed (fixed)

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

boris sondagh’s picture

Status:Closed (fixed)» Active

Still happening when updating from rc6.
I've tested updates to 1.1 / 1.2 / rc7

boris sondagh’s picture

Issue summary:View changes

Updated issue summary.

1n05’s picture

Issue summary:View changes

"Still happening when updating from rc6.
I've tested updates to 1.1 / 1.2 / rc7"...

Any ideas?