I'm using drupal 6.9 and postgresql 8 and I got several erros. Everytime I try to create any content, even a content with no connection with ejournal, I get this:

# warning: pg_query() [function.pg-query]: Query failed: ERROR: sintaxe de entrada inválida para integer: "" in /var/www/melro.ginux.ufla.br/htdocs/bazar-teste/includes/database.pgsql.inc on line 139.
# user warning: query: SELECT jid FROM ejournal_articles WHERE nid='' in /var/www/melro.ginux.ufla.br/htdocs/bazar-teste/modules/ejournal/ejournal.module on line 2500.
# warning: pg_query() [function.pg-query]: Query failed: ERROR: sintaxe de entrada inválida para integer: "" in /var/www/melro.ginux.ufla.br/htdocs/bazar-teste/includes/database.pgsql.inc on line 139.
# user warning: query: SELECT jid FROM ejournalshortly WHERE nid='' in /var

when I edit an issue, I get this:

* warning: pg_query() [function.pg-query]: Query failed: ERROR: para SELECT DISTINCT, expressões ORDER BY devem aparecer na lista do select in /var/www/melro.ginux.ufla.br/htdocs/bazar-teste/includes/database.pgsql.inc on line 139.
* user warning: query: SELECT DISTINCT n.nid, n.type, n.title, n.changed, n.status, n.moderate, t.tid, td.name, ea.iid, ea.weight AS article_weight, ea.proofreader_mark AS p_status FROM (SELECT DISTINCT ON (nid) * FROM node) n INNER JOIN ejournal_articles ea ON n.nid = ea.nid LEFT JOIN term_node t ON n.nid=t.nid LEFT JOIN term_data td ON t.tid=td.tid WHERE ea.iid='1' AND ea.jid='1' ORDER BY ea.weight ASC, td.weight ASC, td.name ASC, n.title ASC in /var/www/melro.ginux.ufla.br/htdocs/bazar-teste/modules/ejournal/ejournal.module on line 2255.

this not happen with mysql, so...

CommentFileSizeAuthor
#2 ejournal-psql.patch2.48 KBfernao
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

nobios’s picture

Assigned: Unassigned » nobios
Status: Active » Postponed

The querys to work in postgre are only changed in the install, not in all code base.. Maybe will see this later on...

fernao’s picture

FileSize
2.48 KB

Hi there!

I'm making an experience with ejournal and I really like PostgreSQL. I had the same errors.

But I've created a patch. For me, it worked; I've made a preliminary test and it worked with postgresql AND mysql.

cheers,

Fernão