PDOException: SQLSTATE... Base table or view not found when unsubscribing by hash

Was this a fresh install or an upgrade?

If you visit update.php are there updates to run?

Were there any errors when you enabled the module?

Are you using MySQL or Postgres?

That table should be created on every site - http://drupalcode.org/project/comment_notify.git/blob/refs/heads/7.x-1.x... so if it doesn't exist on your site then there could be a problem with install/upgrade or with the installation on your site.

Can you try to disable the module, uninstall it, and re-enable it?

It's been more than 2 weeks and nobody else has this problem so closing this issue.

Please do reopen it if you can find the source of the problem.

Hi. I have same problem with fresh install of comment notify 7.x-1.2.
In report I have errorr:
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'drozdu_mydomain.comment_notify' doesn't exist: SELECT c.cid FROM {comment} c, ( SELECT oc.nid, oc.uid FROM {comment} AS oc, comment_notify AS ocn WHERE oc.cid = ocn.cid AND ocn.notify_hash = :hash ) AS o WHERE o.nid = c.nid AND o.uid = c.uid; Array ( [:hash] => kwU3qGq4QkHrkfch853z5z_BNwZggBEJ_fEy5YU1ZF8 ) в функции comment_notify_unsubscribe_by_hash() (строка 278 в файле /hsphere/local/home/drozdu/mydomain.com/sites/all/modules/comment_notify/comment_notify.inc).

Hi, too:
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'prj_ololo.comment_notify' doesn't exist: SELECT c.cid FROM {comment} c, ( SELECT oc.nid, oc.uid FROM {comment} AS oc, comment_notify AS ocn WHERE oc.cid = ocn.cid AND ocn.notify_hash = :hash ) AS o WHERE o.nid = c.nid AND o.uid = c.uid; Array ( [:hash] => d57N0dmWv04ryhTVb7m85R6i6ObEk9cQrcZiUuDt0Mg ) в функции comment_notify_unsubscribe_by_hash() (строка 278 в файле /home/projects/prj_ololo/domain/public_html/sites/all/modules/comment_notify/comment_notify.inc).

PHP 5.4

It seems that there is no table prefix:
Table 'prj_ololo.comment_notify'

And I have a table with a prefix "main_", ie:
Table 'prj_ololo.main_comment_notify'

AHA - that's a great detail.

Can you try this patch?

Excellent! It's working! And here there is no problem?

function comment_notify_unsubscribe_by_hash($hash) {
  $notification = db_select('comment_notify')
      ->fields('comment_notify')
      ->condition('notify_hash', $hash)
      ->execute()->fetchAll();

  // If this notification is at the node level, delete all notifications for this node.
  if (COMMENT_NOTIFY_NODE == $notification[0]->notify) {
    // Get all this user's comments for this node.
    $result = db_query("SELECT c.cid
      FROM {comment} c, (
        SELECT oc.nid, oc.uid
        FROM {comment} AS oc, {comment_notify} AS ocn
        WHERE oc.cid = ocn.cid
        AND ocn.notify_hash = :hash
      ) AS o
      WHERE o.nid = c.nid
      AND o.uid = c.uid", array(':hash' => $hash));

    $cids = $result->fetchCol();

    // Update all comment notifications to be disabled.
    return (bool)db_update('comment_notify')
      ->fields(array(
        'notify' => 0,
      ))
      ->condition('cid', $cids, 'IN')
      ->execute();
  }
  else {
   // Update this notification to be disabled.
   return (bool)db_update('comment_notify')
     ->fields(array(
       'notify' => 0,
     ))
    ->condition('notify_hash', $hash)
    ->execute();
  }
}

That is to say, here:

  $notification = db_select('comment_notify')
      ->fields('comment_notify')
      ->condition('notify_hash', $hash)
      ->execute()->fetchAll();

or here:

  else {
   // Update this notification to be disabled.
   return (bool)db_update('comment_notify')
     ->fields(array(
       'notify' => 0,
     ))
    ->condition('notify_hash', $hash)
    ->execute();
  }

'comment_notify' => {comment_notify}

No?
I'm sorry, I almost do not know Drupal :)

The new database API automatically prefixes tables, so there is no problem with those instances.

Committed to 7.x-1.x - http://drupalcode.org/project/comment_notify.git/commit/d56ea59

I'll probably leave it as part of the dev for a while (that tar file will get re-rolled in the next ~12 hours) so people affected by this bug should wait 12 hours and then upgrade. If there aren't many new bug reports I'll make a new stable release in ~2 weeks.

Is this going to be added to a new stable release? Thanks.

Sure, I just created https://www.drupal.org/node/2599928