From: | "Jose' Soares Da Silva" <sferac(at)bo(dot)nettuno(dot)it> |
---|---|
To: | Byron Nikolaidis <byronn(at)insightdist(dot)com> |
Cc: | interfaces postgres <pgsql-interfaces(at)postgreSQL(dot)org> |
Subject: | Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs |
Date: | 1998-06-12 17:37:29 |
Message-ID: | Pine.LNX.3.96.980612173439.3762B-100000@proxy |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces pgsql-sql |
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'
From | Date | Subject | |
---|---|---|---|
Next Message | eric | 1998-06-12 17:58:27 | Authentication problem |
Previous Message | Jose' Soares Da Silva | 1998-06-12 17:33:57 | Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs |
From | Date | Subject | |
---|---|---|---|
Next Message | Brook Milligan | 1998-06-12 20:39:25 | finding rows in one table not in another |
Previous Message | Jose' Soares Da Silva | 1998-06-12 17:33:57 | Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs |