"Unknown column 'DRUPAL_AUTHENTICATED_RID'" on new install

2.x is great, thanks for your support. And I'm still use 1.9 in production, I have a testing environment, please let me know if you need somebody to test the new functions.

Sorry, it seems not working. This is my test result for 2.0beta7, you can try it from http://drupal5.no-ip.org/?q=node/1 (This is Drupal 5.5)

Test 1:
I upgraded a test site from subscription 1.9 to 2.0 beta 7, and when I added a new comment, I saw this message in watchdog.

Column 'send_comments' in where clause is ambiguous query: INSERT INTO subscriptions_queue (uid, name, mail, language, module, field, value, author_uid, send_interval, digest, last_sent, load_function, load_args) SELECT u.uid, u.name, u.mail, u.language, s.module, s.field, s.value, s.author_uid, s.send_interval, su.digest, su.last_sent, 'subscriptions_content_comment_load', '12' FROM subscriptions s INNER JOIN subscriptions_user su ON s.recipient_uid = su.uid INNER JOIN users u USING(uid) WHERE s.module = 'node' AND s.field = 'type' AND s.author_uid IN (0, -1) AND send_comments = 1 AND s.value = 'blog' AND s.recipient_uid != 0 in D:\00www\WWW\main\includes\database.mysql.inc on line 172.

Test 2:
I installed 2.0 beta7 in another testing site (without 1.9), when I enabled it, I saw this message
user warning: Unknown column 'DRUPAL_AUTHENTICATED_RID' in 'field list' query: INSERT INTO dr_subscriptions_user (uid, digest, send_interval, send_updates, send_comments) VALUES(-DRUPAL_AUTHENTICATED_RID, 0, 1, 0, 0) in D:\00www\WWW\main\includes\database.mysql.inc on line 172.

Then I use anonymous account and admin account to post a comment and get this warning message: (The same as test 1)

user warning: Column 'send_comments' in where clause is ambiguous query: INSERT INTO dr_subscriptions_queue (uid, name, mail, language, module, field, value, author_uid, send_interval, digest, last_sent, load_function, load_args) SELECT u.uid, u.name, u.mail, u.language, s.module, s.field, s.value, s.author_uid, s.send_interval, su.digest, su.last_sent, 'subscriptions_content_comment_load', '1' FROM dr_subscriptions s INNER JOIN dr_subscriptions_user su ON s.recipient_uid = su.uid INNER JOIN dr_users u USING(uid) WHERE s.module = 'node' AND s.field = 'nid' AND s.author_uid IN (0, -1) AND send_comments = 1 AND s.value = '1' AND s.recipient_uid != 0 in D:\00www\WWW\main\includes\database.mysql.inc on line 172. 

I patch the 2 patched but still got 3 error messages in watchdog when I add a new comment (upgrade and new install), but I'm not sure this is due to subscription module because these error messages are in node.module and database.mysql.inc. Do you have any suggestion for it? thanks.

    * warning: Invalid argument supplied for foreach() in D:\00www\WWW\main\modules\node\node.module on line 521.
    * warning: implode() [function.implode]: Bad arguments. in D:\00www\WWW\main\modules\node\node.module on line 525.
    * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM dr_node n INNER JOIN dr_users u ON u.uid = n.uid INNER JOIN dr_node_revisions r ON r.vid = n.vid WHERE in D:\00www\WWW\main\includes\database.mysql.inc on line 172.

I got the problem, when I disabled Comment Notify module, it's ok now.

There is only one successful message "Comment: added test 1." in watchdog now. But I still doesn't receive the mail.

1. I enabled all subscription modules including mail editor 1.1 but I didn't change any configuration of it.
2. For mail module, I use SMTP, it's ok for 1.9 and I can send a test mail from it now.
3. For subscription module, I enabled "Display watchdog entries for successful mailings". For the subscribe option of a post, please see the attachment.

Yes, it's ok now. After the cron, the mails are sent.

Thanks for your support, I think this issue could be closed.