Hi all !
I installed Drupal 6, with several modules, and I enjoy it.
But there are always several warning / error PostgreSQL messages.
For example, in the forum :
warning: pg_query() [function.pg-query]: Query failed: ERROR: syntax error at or near "ON" at character 31 in /var/www/tekover/dev/v3/includes/database.pgsql.inc on line 138.
warning: pg_query() [function.pg-query]: Query failed: ERROR: syntax error at or near "timestamp" at character 90 in /var/www/tekover/dev/v3/includes/database.pgsql.inc on line 138.
I think some of them are due to the ACL/Forum_access modules, which are in beta version, but I got others even if I uninstalled these modules.
Is it "normal" ?
If you want to try it :
- urk : http://tekover.net/dev/v3/forum
- login : test
- password : test
Regards,
Adrien
Comments
Looks like it's the
Looks like it's the "advanced forum" module that's causing those errors. Try uninstall the modules one by one until you find out for definite which it is, then post in that module's issue queue (well, search first...)
Hope that helps!
Cheers
Mark
Code Baboon
Drupal based services
Without this module, I get
Without this module, I get "only" one warning :
warning: pg_query() [function.pg-query]: Query failed: ERROR: syntax error at or near "timestamp" at character 90 in /var/www/tekover/dev/v3/includes/database.pgsql.inc on line 138.
I remember I always had this message since the first setup ...
How can I resolve it ?
It depends how much of a
It depends how much of a developer you are ... ;)
The problem is that the error is being thrown from a generic function (database.pgsql.inc), so it's tough to know where it originates. I am willing to bet that it's not a bug in core, but since you say you had it from first setup, you need to replicate that environment and test.
Start with a blank install of Drupal (no addon modules). Hook it up to a blank PGSQL database... do you get that error still? If so, you need to file a bug against the Drupal issue queue describing exactly what hardware / servers you are using.
However, I am fairly sure it's a module that's throwing this error. So, disable everything one by one and see when it stops
Then you'll know which module it is... ;)
Cheers
Mark
Code Baboon
Drupal based services