Schema 7 fails on PostgreSQL [#1279418]

Has Schema 7.x-1.x even been tested on PostgreSQL? I just did a test install on a brand-new PostgreSQL-backed Drupal site. Going to admin/report/status or admin/structure/schema results in this error:

PDOException: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens: SELECT * FROM information_schema.COLUMNS WHERE table_catalog=:database AND table_schema=current_schema()ORDER BY table_name, ordinal_position; Array ( [:database] => test7 [:table] => ) in schema_compare_schemas() (line 220 of /home/test7/public_html/sites/all/modules/schema/schema.module).

I found the Schema module very handy on Drupal 6, but this is not encouraging.

Comment	File	Size	Author
#2	schema-postgresql-1279418-2.patch	7.44 KB	nohup
#1	Fix_Postgres_Token_count_error-1279418-1.patch	1.07 KB	ben coleman

Comments

Comment #1

ben coleman commented 14 September 2011 at 19:19

Status	File	Size
new	Fix_Postgres_Token_count_error-1279418-1.patch	1.07 KB

Ok, I've got the above error figured out. The problem is that the SELECT has only 1 bound variable, while 2 tokens are provided. The attached patch fixes that.

There are still problems, though. Though this patch fixes the above error message, going to admin/report/status or admin/structure/schema now results in an HTTP Error 500 and a blank page.

Comment #2

nohup commented 29 February 2012 at 04:58

Status	File	Size
new	schema-postgresql-1279418-2.patch	7.44 KB

Ben,

Thanks for your patch. I have updated it to drupal 7 db api.

Patch attached.

Comment #3

ben coleman commented 1 March 2012 at 03:25

Status:

Active

» Reviewed & tested by the community

I can confirm that patch 2 gets rid of the HTTP Error 500 problem. With this patch, admin/structure/schema and admin/report/status at least produce output. There are still problems (and I'll open other issues on them), but Schema 7 no longer fails utterly on PostgreSQL.

Comment #4

lquessenberry commented 27 June 2012 at 18:05

I can't get either one to patch at all.

Comment #5

lquessenberry commented 27 June 2012 at 18:12

I have tried several times to patch this with no luck in patching. I have tried reading all the documentation on patching modules with no avail. When I try to run the patches I get hunk errors or file not found errors. Is there a way someone could commit this to a dev module or just give me a patched version of the module. I am having no luck successfully patching at all.

*UPDATE* I was patching the wrong file. So Sorry! :(