Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org (8.8.8/8.7.5) with ESMTP id RAA15618 for ; Thu, 11 Jun 1998 17:59:15 -0400 (EDT) Received: from insightdist.com (nobody@localhost) by u1.abs.net (8.9.0/8.9.0) with UUCP id RAA12936 for pgsql-interfaces@postgreSQL.org; Thu, 11 Jun 1998 17:40:03 -0400 (EDT) X-Authentication-Warning: u1.abs.net: nobody set sender to insightdist.com!byronn using -f Received: from ceodev by insightdist.com (AIX 3.2/UCB 5.64/4.03) id AA34397; Thu, 11 Jun 1998 17:37:07 -0400 Received: from [3.0.0.50] by ceodev (AIX 4.1/UCB 5.64/4.03) id AA24496; Thu, 11 Jun 1998 17:37:06 -0400 Message-Id: <35804DC3.55CB1496@insightdist.com> Date: Thu, 11 Jun 1998 17:36:03 -0400 From: Byron Nikolaidis X-Mailer: Mozilla 4.05 [en] (Win95; I) Mime-Version: 1.0 To: "Jose' Soares Da Silva" Cc: interfaces postgres Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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. Byron