Postgres Pro
Downloads
Home   >   mailing lists

Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons - Mailing list pgsql-odbc

From Jack Wilson
Subject Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons
Date
Msg-id OFF0EF4C96.FCE41E17-ON85257405.006B3A3D-85257405.006CE95F@digitalav.com
Whole thread Raw
In response to Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons  (Hiroshi Inoue <inoue@tpf.co.jp>)
Responses Re: Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons  (alepaes - aldeia digital <alepaes@aldeiadigital.com.br>)
List pgsql-odbc
Tree view

Hiroshi,

I get slightly different error now:

Error: 42601 ERROR: syntax error at or near "a";

Here is the sql statement with the trailing semicolon I'm testing with--substitute a valid table name for the word 'my_table' below:

SELECT  pg_attribute.attname, pg_attribute.attnotnull, pg_attribute.atttypmod, pg_type.typname  
FROM  pg_attribute  
JOIN  pg_class ON pg_attribute.attrelid = pg_class.oid  
JOIN  pg_namespace ON pg_namespace.oid = pg_class.relnamespace  
JOIN  pg_type on pg_type.oid = pg_attribute.atttypid  
where  pg_namespace.nspname = 'public'
AND  pg_class.relname = 'my_table' and  pg_class.relkind = 'r' and  pg_attribute.attnum > 0  
ORDER BY  pg_attribute.attnum;

Thanks...jack
--
********************************************
Who:    L Jack Wilson
Where:  ljwilson@dNiOgSiPtAaMlav.com
How:    Remove Capital Letters from above for a valid email address
Why:    Standard Disclaimer fits nicely here.

pgsql-odbc by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: Cannot get psqlODBC to work
Next
From: Glyn Astill
Date:
Subject: Re: Cannot get psqlODBC to work