Dave Page wrote:
> I've recently come across a couple of minor problems(?) in the ODBC driver:
> 1) When querying a view eg:
> SELECT * FROM pg_tables;
> the driver will always attempt (and fail) to retrieve the oid column thus
> returning an ODBC call failed error. This occurs whether the 'Show OID
> Column' is selected or not. I can see the obvious overhead in checking
> whether or not a query is on a view or table - is the current behaviour the
> best solution or is there another way around this (other than specifying
> column names in queries)?
I'm not sure what you mean by "the driver will always attempt to retrieve the oid
column"... What is the driver doing? If it is sending another query, could you show
me exactly what because its been a while since I looked at the code.
> 2) Under OID options, if you uncheck 'Show Column', the 'Fake Index' option
> will correctly be greyed out. If it is ticked when it is greyed though, the
> driver will still connect with: showoid='0',fakeoidindex='1'. Can this cause
> any problems?
I dont think so, but I'm not 100% sure.
In response to
pgsql-interfaces by date
|Next:||From: Stan Brown||Date: 1999-06-29 14:35:23|
|Subject: ODBC info?|
|Previous:||From: Byron Nikolaidis||Date: 1999-06-29 13:35:29|
|Subject: Re: [INTERFACES] ODBC and Access 2000: linked tables problem|