From: | "Paragon Corporation" <lr(at)pcorp(dot)us> |
---|---|
To: | <pgadmin-support(at)postgresql(dot)org> |
Subject: | Bug: Foreign Data Table DDL SQL is mangled |
Date: | 2012-04-16 13:12:14 |
Message-ID: | 21344D49106341B99602E3EBF6164E95@D |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
I'm testing on Windows 2008 64-bit pgAdmin 1.14.2
I used the odbc_fdw based foreign data table that I created with this
statement:
CREATE FOREIGN TABLE my_tables
(table_catalog character varying(128) ,
table_schema character varying(128) ,
table_name character varying(128) ,
table_type character varying(128) )
SERVER localsql2005
OPTIONS (database 'myserver2005', sql_query 'SELECT CAST(TABLE_CATALOG As
varchar(128)) As table_catalog
, CAST(TABLE_SCHEMA As varchar(128)) As table_schema, CAST(TABLE_NAME As
varchar(128)) As table_name
, CAST(TABLE_TYPE As varchar(128)) As table_type
FROM information_schema.tables', sql_count 'select count(TABLE_NAME) from
information_schema.tables');
When I use pgAdmin to regenerate the SQL ddl for it, it generates this
malformed thing that can't be run:
CREATE FOREIGN TABLE my_tables
(table_catalog character varying(128) ,
table_schema character varying(128) ,
table_name character varying(128) ,
table_type character varying(128) )
SERVER localsql2005
OPTIONS (database 'myserver2005', sql_query 'SELECT CAST(TABLE_CATALOG As
varchar(128)) As table_catalog
, CAST(TABLE_SCHEMA As varchar(128)) As table_schema, CAST(TABLE_NAME As
varchar(128)) As table_name
, CAST(TABLE_TYPE As varchar(128)) As table_type
FROM information_schema.tables', ,"sql_count 'select count(TABLE_NAME) from
information_schema.tables"');
Thanks,
Regina
From | Date | Subject | |
---|---|---|---|
Next Message | Paragon Corporation | 2012-04-16 13:15:09 | Feature Request: No gui for creating user mappings |
Previous Message | Dennis | 2012-04-13 18:42:40 | Uniform UPDATE queries |