Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] ODBC: OID column in views

From: José Soares <jose(at)sferacarta(dot)com>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: [INTERFACES] ODBC: OID column in views
Date: 1999-06-30 12:31:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
I have a problem similar about RowVersioning.
If I link a view with RowVersioning checked M$Access show the following message, when I
try to open the table:

Error while executing the query.
ERROR: system column xmin not available - table_name is a view (#1)

Dave Page ha scritto:

> 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)?
> 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?
> Regards,
> Dave.

PostgreSQL 6.5.0 on i586-pc-linux-gnu, compiled by gcc

In response to

pgsql-interfaces by date

Next:From: Bryan WhiteDate: 1999-06-30 13:29:08
Subject: Default values not working
Previous:From: Moray McConnachieDate: 1999-06-30 09:36:37
Subject: Re: [INTERFACES] ODBC and Access 2000: linked tables problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group