Message-ID: <377A0E2A.2E2611AB@sferacarta.com>
Date: Wed, 30 Jun 1999 14:31:38 +0200
From: =?iso-8859-1?Q?Jos=E9?= Soares <jose@sferacarta.com>
MIME-Version: 1.0
To: Dave Page <dpage@vale-housing.co.uk>
CC: "'pgsql-interfaces@postgresql.org'" <pgsql-interfaces@postgresql.org>
Subject: Re: [INTERFACES] ODBC: OID column in views
References: <B9FE686F5C26D311AC22006097BCD3D65EFC@woody.vale-housing.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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 2.7.2.3
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jose'