From: Hannu <hannu@trust.ee>
To: Byron Nikolaidis <byronn@insightdist.com>
To: interfaces postgres <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
Date: Fri, 12 Jun 1998 10:45:38 +0300
Message-ID: <3580DCA2.6ED9826E@trust.ee> (raw)
References: <Pine.LNX.3.96.980611112320.3708A-100000@proxy>
<357FFD63.2329E3FA@insightdist.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: hannu@trust.ee, byronn@insightdist.com
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
In-Reply-To: <3580DCA2.6ED9826E@trust.ee>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox