Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I am fairly new to drupal, and this was working in page_title-6.x-2.0 after updating the mod I get this error:
warning: pg_query() [function.pg-query]: Query failed: ERROR: column "node" does not exist LINE 1: SELECT page_title FROM page_title WHERE type = "node" AND id... ^ in /usr/local/www/apache22/drupal.techally.com/public/includes/database.pgsql.inc on line 139.
user warning: query: SELECT page_title FROM page_title WHERE type = "node" AND id = 2 in /usr/local/www/apache22/drupal.techally.com/public/sites/all/modules/page_title/page_title.module on line 302.
I included a screen shot just in case.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | page_title_pgsql_quote.patch | 3.28 KB | macedigital |
| #6 | page_title_pgsql_quote.patch | 1.44 KB | jianingy |
| #5 | page_title.patch | 494 bytes | valthebald |
| page_title_error.png | 36.77 KB | matreides |
Comments
Comment #1
porcelaindev commentedI'm having exactly the same problem but on D5. When I de-activate page_title module the error goes away. Any ideas?
Comment #2
nicholasthompsonAh this would be my fault as I've not included an upgrade path for PGSQL (completely forgot about that! Sorry!)...
Does anyone have any experience with PGSQL? I've never used it and the syntax looks a little different to MySQL. I believe it's update 5203 and 6200 which do the MySQL updating...
Comment #3
xzilla commentedThe problem is that MySQL uses non-standard quoting, so your SQL won't work on Postgres. For Postgres, you need to quote identifiers (table names,column names,view names,etc...) using ", and literal values (text,timestamps,etc...) using '. So your above query should look like this:
SELECT page_title FROM page_title WHERE type = 'node' AND id = 2;
Note: I believe there is a way to get MySQL to accept the standard quoting, but don't recall off-hand how it's done. HTH.
Comment #4
luti commentedxzilla, what do you mean by "The problem is that MySQL uses non-standard quoting..."?
As much as I know, it is just fine for MySQL to query:
SELECT page_title FROM page_title WHERE type = "node" AND id = 2or
SELECT page_title FROM page_title WHERE type = 'node' AND id = 2Both shall work well, and return the same result.
You shall of course switch the whole query sentence from single quotes to double quotes, to make a difference... ;-)
Comment #5
valthebaldProblem is caused by the fact PostgreSQL distincts ' from "
Attached (very small) patch fixes the problem
Comment #6
jianingy commentedPostgreSQL uses quotes for only field names.
Attached patch fixes this problem not only for SELECT query but also INSERT and DELETEs.
Comment #7
macedigital commentedLike valthebald said, postgres makes a distinction between single-quotes and double-quotes. Second Problem is with column "type" which is a reserved word in postgres.
So I made a patch against page_title version 6.x-2.2 featuring :
- "type" as a column name should always be double-quoted just to make sure
- 'node' / 'user' / 'term' as a plain string must be single-quoted
Hopefully, I didn't miss something,
Cheers
Comment #8
gugrim commentedThe double quoted string values does not work with MySQL either if it is configured to accept ANSI SQL. I'm having the same problem with MySQL and the page_title module.
Comment #9
nicholasthompsonI have applied the fix from #622928: PostgreSQL compatibility - this should solve this. Please re-open if it is still broken (Fix currently in 6.x-2.x-dev... Will be in 2.4)...