From: | "Wayne Armstrong" <wdarmst(at)bacchus(dot)com(dot)au> |
---|---|
To: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Parse statement can fail for unquoted uppercase tablenames |
Date: | 2003-04-10 04:57:28 |
Message-ID: | 200304100459.h3A4xHdv022362@mail.bacchus.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hi,
If I pass the odbc driver a statement that looks like :-
select * from CALEND_EVENT
and statement parsing is turned on it may fail if it tries to do a
PGAPI_Columns call using the following SQL:-
select u.nspname, c.relname, a.attname, a.atttypid, t.typname, a.attnum,
a.attlen, a.atttypmod, a.attnotnull, c.relhasrules, c.relkind from pg_namespace
u, pg_class c, pg_attribute a, pg_type t where u.oid = c.relnamespace and (not
a.attisdropped) and c.oid= a.attrelid and a.atttypid = t.oid and (a.attnum > 0)
and c.relname = 'CALEND_EVENT' and u.nspname = 'bacchus' order by u.nspname,
c.relname, attnum.
select * from calend_event
works fine.
So even though the tablename is not quoted (and thus should be folded to
lowercase), the statement may return no rows, cause the columncount returned
from the statement parsing is 0.
Regards,
Wayne
From | Date | Subject | |
---|---|---|---|
Next Message | Wayne Armstrong | 2003-04-10 06:02:15 | Re: Parse statement can fail for unquoted uppercase tablenames |
Previous Message | Daniel F Garcia | 2003-04-10 03:56:34 | Connection to posgresql database works under windows scripting host but not IIS/ASP |