Received: from proxy.bazzanese.com (sferac@ip154.tol11.interbusiness.it [195.120.106.154]) by hub.org (8.8.8/8.7.5) with ESMTP id LAA12675 for ; Fri, 12 Jun 1998 11:44:44 -0400 (EDT) Received: from localhost (sferac@localhost) by proxy.bazzanese.com (8.8.8/8.8.8/Debian/GNU) with SMTP id RAA03816; Fri, 12 Jun 1998 17:37:29 GMT Date: Fri, 12 Jun 1998 17:37:29 +0000 (UTC) From: "Jose' Soares Da Silva" X-Sender: sferac@proxy To: Byron Nikolaidis cc: interfaces postgres Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs In-Reply-To: <358133C2.9429A8F8@insightdist.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 12 Jun 1998, Byron Nikolaidis wrote: > > > 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 Good. > 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. I beleave we don't need that Access recognize timestamp as a ROWVER, now that we have an xmin that do this. Thanks, Jose'