Received: from sid.trust.ee (sid.trust.ee [194.204.23.180]) by hub.org
	(8.8.8/8.7.5) with ESMTP id DAA17808 for
	<pgsql-interfaces@postgreSQL.org>;
	Fri, 12 Jun 1998 03:49:58 -0400 (EDT)
Received: from trust.ee (bonk.trust.ee [194.204.23.190])
	by sid.trust.ee (8.8.7/8.8.7) with ESMTP id KAA01036;
	Fri, 12 Jun 1998 10:49:58 +0300
Message-ID: <3580DCA2.6ED9826E@trust.ee>
Date: Fri, 12 Jun 1998 10:45:38 +0300
From: Hannu <hannu@trust.ee>
Reply-To: hannu@trust.ee
Organization: Trust-O-Matic OÜ
X-Mailer: Mozilla 4.05 [en] (WinNT; I)
MIME-Version: 1.0
To: Byron Nikolaidis <byronn@insightdist.com>,
	interfaces postgres <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
References: <Pine.LNX.3.96.980611112320.3708A-100000@proxy>
	<357FFD63.2329E3FA@insightdist.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Byron Nikolaidis wrote:
> 
> Hi,
...
> 
> I have tested other types besides timestamps, like int4, and they seem
> to work fine as a versioning column.  So, we could use the postgres
> 'xmin' column, if we displayed it in SQLColumns.  It seems to always
> update so you wouldn't have to worry about a trigger.  I'm not sure what
> end-users would think about seeing these ugly columns in Access?  Any
> thoughts about that?

Is'nt there some way in ODBC to return some kind of _system_ columns, 
like there are system tables ?

I think that PostgreSQL is not the only database that has system columns 

Hannu