"Base table or view not found" if we have a prefix for tables.

This is also an issue in the 8.x branch, manually replacing { @table_name } with {@table_name} in the corresponding files fixes it.

Upgraded to Drupal core 7.78 today and got a new error like the one below, which this patch solves for us by removing the spaces. Since we are not using table prefixes, I don't think prefix is pertinent to this issue ie. it will happen all the time on latest Drupal core since 7.76, I believe, when changes were made in handling table names in preparation for MySQL 8.

PDOException: SQLSTATE[42000]: Syntax error or access violation: 1103 Incorrect table name ' table_name_here ': DESCRIBE { table_name_here }; Array ( ) in view_custom_table_views_data() (line 174 of /path/to/view_custom_table.module).

Had the same error than darkodev after a Drupal core update, seems effectively related to the Drupal 7.76 release where some changes were made at the table name quoting level. Patch #2 succesfully fixes the issue and should be merged urgently to a new Views Custom Table 7.x release because currently it breaks down any up-to-date Drupal 7 website.

I've just had this issue again on a site and found this issue here then realised that I've created the exact same solution on this duplicate issue here and forgot about it :))
https://www.drupal.org/project/view_custom_table/issues/3186756

The patches are exactly the same and in both cases have been reviewed by several users so should probably be committed to the module as people seem to keep facing this issue.

Thanks for the fix, I'll cut a new 7.x release shortly.

New release for Drupal 7 , version 7.x-1.0

download version 7.x-1.0