pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Byron Nikolaidis <byronn@insightdist.com>
To: Jose' Soares Da Silva <sferac@bo.nettuno.it>
Cc: interfaces postgres <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
Date: Fri, 12 Jun 1998 09:57:22 -0400
Message-ID: <358133C2.9429A8F8@insightdist.com> (raw)
References: <Pine.LNX.3.96.980612100622.648A-100000@proxy>



Jose' Soares Da Silva wrote:

> Ok Byron, I think this is a good solution.
> In this way we don't need to add a TIMESTAMP to every table there's already a
> XMIN present.
> In any way, what's happen with TIMESTAMPs ? May we have Access recognize it as
> DATETIME or we can't because Access beleaves that's a ROWVER ?
> I would like to try it. Please Byron may you send me the code for '=' operator
> for xid type.
>                                                          Jose'


I added the postgres timestamp type and mapped it to SQL_TIMESTAMP, so Access recognizes it
now as a Date/Time.  It does not automatically recognize it is a ROWVER.  Did you read
somewhere that it did that?  In my testing it never did, UNLESS, I mentioned the column in
SQLSpecialColumns and specifically said it was a ROWVER.

Byron

P.S., Dave Hartwig is sending you the code for the xid '=' operator.





view thread (27+ messages)  latest in thread

Message-ID: <358133C2.9429A8F8@insightdist.com>
Permalink:  ../358133C2.9429A8F8@insightdist.com/
Also on:    postgresql.org/message-id/358133C2.9429A8F8@insightdist.com

 · 

reply

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, sferac@bo.nettuno.it
  Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
  In-Reply-To: <358133C2.9429A8F8@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