i get this error message on the /subscriptions page.

user warning: Column 'description' in field list is ambiguous query: SELECT type, description, send_interval, stype FROM main_privatemsg_mail_edit p LEFT JOIN main_mail_edit m ON p.mailkey = m.mailkey LEFT JOIN main_subscriptions s ON concat('pmsg', type) = stype AND uid = 1 ORDER BY type in /home/mykart/public_html/drupal5/includes/database.mysql.inc on line 172.

is this because there is the same field in the mail_edit and privatemsg_mail_edit tables?

Comments

salvis’s picture

salvis
he/his
commented
Title: error message on subscriptions page » /subscriptions: "Column 'description' in field list is ambiguous query"

main_privatemsg_mail_edit should only have two columns, type and mailkey. Have you manipulated the database tables?

You don't have any live data in Subscriptions and Privatemsg yet, right? I'd suggest you download the current snapshots of these two modules, deactivate and uninstall (/admin/build/modules/uninstall) them as well as Mail Editor, and then reinstall them.

TheFazz’s picture

TheFazz commented

i don't think i had manipulated the tables, although i did do a manual table update for a problem i was having with the privatemsg http://drupal.org/node/164943

i did a mysql update based on post#9.

salvis’s picture

salvis
he/his
commented

I don't think the poster in http://drupal.org/node/164943#comment-288033 (#9) knew what he was doing. The main_privatemsg_mail_edit.description column didn't come from that post though.

Anyway, please start over from scratch according to #1.

Also keep in mind, that this is work in progress and there is no 2.0 release yet. -dev snapshots should not be used on production sites unless there's overwhelming evidence that it's safe to do so.

TheFazz’s picture

TheFazz commented

thanks salvis. unfortunately, i had not kept a backup of the tables before the 2.x-dev upgrades of privatemsg and subscriptions... so reverting back to the previous version is a little more complex (& manual).

if there is a way to revert, then i will do so. otherwise, i shall persist with the latest version. the risks are acceptable at this juncture.

salvis’s picture

salvis
he/his
commented

Then I'd suggest to either make a test installation from scratch or go through all three .install files (with their update_N() functions) to assemble the correct table definitions, and review and fix each of the tables.

salvis’s picture

salvis
he/his
commented
Status: Active » Fixed

Marking this fixed, as the issue is not in the current snapshot.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)