Re: [INTERFACES] postgresODBC and Symantec dbAnywhere/Visual Cafe, broken?

From: David Hartwig <daveh(at)insightdist(dot)com>
To: Matthew Hagerty <matthew(at)wolfepub(dot)com>
Cc: pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] postgresODBC and Symantec dbAnywhere/Visual Cafe, broken?
Date: 1998-08-06 18:44:51
Message-ID: 35C9F9A3.EB68EE65@insightdist.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Mathew,

I will do my best to sort through this. Byron, the primary author of the driver will be returning from vacation, Monday. I expect he may not get to this until at least the middle of next week. In any case, we do not have dbanywhere here and I am not aware of anyone using the driver for this. But we will get it resolved.

Matthew Hagerty wrote:

> psqlodbc.log
> ------------
> DSN info: DSN='PostgreSQL',server='10.0.0.1',port='5432',dbase='test',user='postgres',passwd='postgres1'
>
> readonly='0',protocol='',showoid='1',fakeoidindex='0',showsystable='0'
> conn_settings=''
> translation_dll='',translation_option=''
> conn = 87033980, SQLConnect(DSN='PostgreSQL', UID='postgres', PWD='postgres1')
> Global Options: fetch=100, socket=4096, unknown_sizes=2, max_varchar_size=254, max_longvarchar_size=4094
> disable_optimizer=1, unique_index=0, use_declarefetch=1
> text_as_longvarchar=0, unknowns_as_longvarchar=0, bools_as_char=1
> extra_systable_prefixes='dd_;', conn_settings=''
> conn=87033980, query=' '
> conn=87033980, query='BEGIN'
> conn=87033980, query='set DateStyle to 'ISO'; set geqo to 'OFF''
> Command response: 'SET VARIABLE'
> conn=87033980, query='declare SQL_CUR87048472 cursor for select oid from pg_type where typname='lo''
> conn=87033980, query='fetch 100 in SQL_CUR87048472'
> [ fetched 0 rows ]
> conn=87033980, query='close SQL_CUR87048472'
> conn=87033980, query='END'
> conn=87033980, query='BEGIN'
> conn=87033980, query='declare SQL_CUR87114156 cursor for select relname, usename, relhasrules from pg_class, pg_user where relkind = 'r' and usename like 'postgres' and relname !~ '^pg_|^dd_' and relname !~ '^xinv[0-9]+' and int4out(usesysid) = int4out(relowner) order by relname'
> conn=87033980, query='fetch 100 in SQL_CUR87114156'
> [ fetched 2 rows ]

Query for database tables.

> conn=87033980, query='close SQL_CUR87114156'
> conn=87033980, query='END'
> conn=87033980, query='BEGIN'
> conn=87033980, query='declare SQL_CUR87114156 cursor for select u.usename, c.relname, a.attname, a.atttypid,t.typname, a.attnum, a.attlen, a.atttypmod, a.attnotnull from pg_user u, pg_class c, pg_attribute a, pg_type t where int4out(u.usesysid) = int4out(c.relowner) and c.oid= a.attrelid and a.atttypid = t.oid and (a.attnum > 0) and c.relname like 'contacts' order by attnum'
> conn=87033980, query='fetch 100 in SQL_CUR87114156'
> [ fetched 10 rows ]

Query for attributes of table 'contacts'.

> conn=87033980, query='close SQL_CUR87114156'
> conn=87033980, query='END'
> conn=87033980, query='BEGIN'
> conn=87033980, query='declare SQL_CUR87193300 cursor for select u.usename, c.relname, a.attname, a.atttypid,t.typname, a.attnum, a.attlen, a.atttypmod, a.attnotnull from pg_user u, pg_class c, pg_attribute a, pg_type t where int4out(u.usesysid) = int4out(c.relowner) and c.oid= a.attrelid and a.atttypid = t.oid and (a.attnum > 0) and c.relname like 'contacts' order by attnum'
> conn=87033980, query='fetch 100 in SQL_CUR87193300'
> [ fetched 10 rows ]

Another query for attributes of table 'contacts'. That client/server for ya.

> conn=87033980, query='close SQL_CUR87193300'
> conn=87033980, query='END'
> conn=87033980, query='BEGIN'
> conn=87033980, query='declare SQL_CUR87114156 cursor for select c.relname, i.indkey, i.indisunique, i.indisclustered from pg_index i, pg_class c, pg_class d where c.oid = i.indexrelid and d.relname = 'contacts' and d.oid = i.indrelid'
> conn=87033980, query='fetch 100 in SQL_CUR87114156'
> [ fetched 0 rows ]

Query for indexes in 'contacts'. Looks like none! Do any indices actually exist? If so, could you cut this query out and run it in the psql monitor and notify me of the results.

> conn=87033980, query='close SQL_CUR87114156'
> conn=87033980, query='END'
> conn=87033980, query='BEGIN'
> conn=87033980, query='declare SQL_CUR87048472 cursor for select distinct on attnum a2.attname, a2.attnum from pg_attribute a1, pg_attribute a2, pg_class c, pg_index i where c.relname = 'contacts_pkey' AND c.oid = i.indexrelid AND a1.attrelid = c.oid AND a2.attrelid = c.oid AND (i.indkey[0] = a1.attnum OR i.indkey[1] = a1.attnum OR i.indkey[2] = a1.attnum OR i.indkey[3] = a1.attnum OR i.indkey[4] = a1.attnum OR i.indkey[5] = a1.attnum OR i.indkey[6] = a1.attnum OR i.indkey[7] = a1.attnum) order by a2.attnum'
> conn=87033980, query='fetch 100 in SQL_CUR87048472'
> [ fetched 0 rows ]

Query for attributes of index 'contact_pkey'. Does this index actually exist? If so, could you cut this query out and run it in the psql monitor and notify me of the results.

In response to

Browse pgsql-interfaces by date

  From Date Subject
Next Message Adam Williams 1998-08-06 19:15:39 QBE Anyone?
Previous Message David Hartwig 1998-08-06 17:44:18 Re: [INTERFACES] Server-side cursors