Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs

From: "Jose' Soares Da Silva" <sferac(at)bo(dot)nettuno(dot)it>
To: David Hartwig <daveh(at)insightdist(dot)com>
Cc: Byron Nikolaidis <byronn(at)insightdist(dot)com>, interfaces postgres <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
Date: 1998-06-12 17:33:57
Message-ID: Pine.LNX.3.96.980612171736.3762A-100000@proxy (view raw or flat)
Thread:
Lists: pgsql-interfacespgsql-sql
I compiled and I installed successful the xid operator, I tried it 
using: SELECT * FROM foo WHERE xmin = {some_constant}
and it works.
I download psqlodbc.dll v06.03.0244, I tried it but seems that doesn't work yet.
Did I forget something ?
Thanks in any way for your work David.
I'm going for vaccations next week, so forgive me if I don't replay for a week.
                                                    Jose'

On Fri, 12 Jun 1998, David Hartwig wrote:
> > > 2) You have to create an '=' operator for the xid type on the postgres side since one
> Here is is what you will need.   I hope you know how to compile a shared lib for your
> platform.  This can be an adventure if you have not done it before.     You will have to
> adjust the path in the CREATE FUNCTION statement to your lib dir.   Run the SQL after you
> compile and install the shared lib.     To test, do something like:
> 
>     SELECT * FROM foo WHERE xmin = {some_constant}
> 
> I plan to submit a patch to make this a part of the 6.4 base release.
> 
> 
> 
> 
> Jose' Soares Da Silva wrote:
> 
> > On Thu, 11 Jun 1998, Byron Nikolaidis wrote:
> >
> > > Jose',
> > >
> > > I got row versioning working with the "xmin" field.  Since it is a system column, and
> > > automatically updates, you would not need triggers all over the place on every table.
> > > I made it a datasource option called "Row Versioning".
> > >
> > > It works well with Access except for two minor caveats:
> > >
> > > 1)  The driver has to report the 'xmin' field in SQLColumns.  There is no way around
> > > that I can see.  Access, thus displays it.  Users can of course hide the column if they
> > > hate looking at it.  And Access won't let you type into this field which is good.
> > >
> > > 2) You have to create an '=' operator for the xid type on the postgres side since one
> > > does not already exist.  I have the code to do it if you are interested (it is very
> > > small).  For 6.4, we would make sure this operator is added.
> > >
> > 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'
> 


In response to

Responses

pgsql-interfaces by date

Next:From: Jose' Soares Da SilvaDate: 1998-06-12 17:37:29
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
Previous:From: Byron NikolaidisDate: 1998-06-12 16:00:44
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs

pgsql-sql by date

Next:From: Jose' Soares Da SilvaDate: 1998-06-12 17:37:29
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
Previous:From: Petter ReinholdtsenDate: 1998-06-12 16:35:53
Subject: Bug in UPDATE RULE?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group