Since #869796: Schema does not work with shared databases (that use prefixes) was closed long time ago and is not re-openable anymore, I had to create this new issue on the same subject. So the problem is the same - with the database connection configured in the settings.php file like so:

$databases['default']['default'] = array(
      'database' => 'domain_domain',
      'username' => 'domain',
      'password' => 'SDdfkj2323DFfd',
      'host' => 'localhost',
      'driver' => 'mysql',
      'prefix' => array(
          'default' => '',
          'users' => 'shared.',
          'users_roles' => 'shared.',
          'sessions' => 'shared.',
          'role' => 'shared.',
          'realname' => 'shared.',
          'sequences' => 'shared.',
          'authmap' => 'shared.',
          'field_data_field_first_name' => 'shared.',
          'field_revision_field_first_name' => 'shared.',
          'field_data_field_last_name' => 'shared.',
          'field_revision_field_last_name' => 'shared.',
          'field_data_field_organization' => 'shared.',
          'field_revision_field_organization' => 'shared.',
          'field_data_field_title' => 'shared.',
          'field_revision_field_title' => 'shared.',
          'field_data_field_about_author' => 'shared.',
          'field_revision_field_about_author' => 'shared.',
    ),
);

everything works ok, however the Schema module reports 17 tables missing:

Missing (17)
Tables in the schema that are not present in the database.

Hide field_sql_storage
field_data_field_title
field_revision_field_title
field_data_field_first_name
field_revision_field_first_name
field_data_field_last_name
field_revision_field_last_name
field_data_field_about_author
field_revision_field_about_author
field_data_field_organization
field_revision_field_organization

Hide realname
realname

Hide system
sequences
sessions

Hide user
authmap
role
users
users_roles

Indeed those tables are not presented on the website's database, however they are pulled from shared database. Shouldn't the Schema module respect the shared database configuration in the settings.php file or is it normal state and we should just ignore the Schema module's report?

Comments

nickonom created an issue.