I had assumed that Access was just treating it like another field
and going for over kill in identifying the record. However this doesn't seem
to be the case as in a quick test it doesn't appear to use any other fields,
not even non null, unique indexed ones. Just the primary key and xmin.
Is xmin a standard for RowVersioning? Does SQL Server use it
perhaps, and allows you to reference it in such a way. (Could this be
related to the problems people had updating using ADO in Access, but they
could outside and also to SQL Server? Never used ADO myself and can't
remember the exact situation that was discussed).
I wonder what other software out there would like to treat xmin as
an int4? Is it an Access thing, an MS thing, or is it more wide spread?
Hmm, better stop rambling now :)
> -----Original Message-----
> From: Tom Lane [SMTP:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Thursday, May 10, 2001 4:13 PM
> To: Chris Gray
> Cc: Henshall, Stuart - WCP; pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] RE: ODBC and Access 2000
> Chris Gray <cpgray(at)library(dot)uwaterloo(dot)ca> writes:
> > Would anyone care explain just what that function and operator are
> Apparently they're meant to allow constructs like "WHERE xmin = 1234"
> to be accepted. What I'd like to know is why Access wants to do that...
> regards, tom lane
pgsql-odbc by date
|Next:||From: Tom Lane||Date: 2001-05-10 20:59:08|
|Subject: Re: RE: ODBC and Access 2000 |
|Previous:||From: Ken Godee||Date: 2001-05-10 17:53:21|
|Subject: Win32 ODBC ?'s|