Message-Id: <358132DF.2262873F@insightdist.com>
Date: Fri, 12 Jun 1998 09:53:35 -0400
From: Byron Nikolaidis <byronn@insightdist.com>
Mime-Version: 1.0
To: hannu@trust.ee
Cc: 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> <3580DCA2.6ED9826E@trust.ee>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hannu wrote:

> 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
>

Yes, the 'pseudo' column attribute in SQLSpecialColumns does this.  I am
setting it for the xmin field, but Access never even bothers to look at it (it
never binds the column or does GetData).  It is only interested in the column
name!?!

You would think that you could report system columns like 'xmin' just in
SQLSpecialColumns and not have to also specify them in SQLColumns.  But as I
said, if I don't also specify the column in SQLColumns, Access barfs with the
message "Table TMP%#MAU@ already exists." when I try to open the table.  The
linking phase works fine though.

It doesn't make much sense.

If you have any ideas what the heck that message means, PLEASE TELL ME!!!!

Byron