From: Byron Nikolaidis <byronn@insightdist.com>
To: hannu@trust.ee
Cc: interfaces postgres <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
Date: Fri, 12 Jun 1998 09:53:35 -0400
Message-ID: <358132DF.2262873F@insightdist.com> (raw)
References: <Pine.LNX.3.96.980611112320.3708A-100000@proxy>
<357FFD63.2329E3FA@insightdist.com>
<3580DCA2.6ED9826E@trust.ee>
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
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: byronn@insightdist.com, hannu@trust.ee
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
In-Reply-To: <358132DF.2262873F@insightdist.com>
* 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