After installing wishlist 4.7.0 I get the following errors:

* warning: pg_query() [function.pg-query]: Query failed: ERROR: Attribute n.nid must be GROUPed or used in an aggregate function in /usr/local/apache2/drupal/includes/database.pgsql.inc on line 84.

* user warning: query: SELECT n.nid, n.title, n.uid, u.name FROM node n INNER JOIN users u ON n.uid = u.uid WHERE n.type='wishlist' GROUP BY u.uid ORDER BY u.name DESC in /usr/local/apache2/drupal/includes/database.pgsql.inc on line 103.

I'm running postgresql and apache on Linux.

Comments

scott.mclewin’s picture

scott.mclewin commented

I don't have an answer for you that I'm too happy with. The Postgres support was contributed to me by another user. I've never run with or tested with postgres. I know that I *should* be doing that, but for me it is a matter of the time I've got to commit to the wishlist module. I aim to be as responsive as I possibly can to issues, but I have set a few limits. I don't intend to configure or run postgres. I'm not proud of this answer. But it is what it is.

If you can reproduce the issue with MySQL I'll address it as a critical issue.

Are you knowledgable enough of php, SQL, Drupal and Postgres to diagnose and address this yourself? If not you might also contact the fellow who contributed the postgres support. The postgres support was contributed by Drupal user toddfries. (http://drupal.org/user/39075) Frankly I don't know if this is a Postgres vs. MySQL issue or not. It also could be a problem in db_rewrite_sql in v 4.7. The table structure of the wishlist module did not change between v4.6 and v4.7.

erwin’s picture

erwin commented

Hi Scott,

All errors that I have seems postgresql related. I think postgresql test the select statement more against the SQL standards than mysql does. I've fixed some of the errors. I will send you the module if it's working here to test it against mysql.

scott.mclewin’s picture

scott.mclewin commented

Excellent. Thanks for your willingness to work with me on fixing this.

scott.mclewin’s picture

scott.mclewin commented
Status: Active » Closed (fixed)

Please re-open or create a new issue with your postgres patch is ready.