RE: Row Versioning, for jdbc updateable result sets

From: "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>
To: "'Dave Cramer'" <dave(at)fastcrypt(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: RE: Row Versioning, for jdbc updateable result sets
Date: 2001-06-15 09:41:37
Message-ID: E2870D8CE1CCD311BAF50008C71EDE8E01F745EC@MAIL_EXCHANGE
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Don't know about JDBC, but couldn't you just use UPDATE <xxx> SET
<yyy>=<zzz> WHERE xmin=<stored/old xmin> AND primarykey=<stored/old pk> and
get the number of altered records? (if its zero then you know somethings
wrong and can investigate further)
- Stuart

> -----Original Message-----
> From: Dave Cramer [SMTP:dave(at)fastcrypt(dot)com]
> Sent: Thursday, June 14, 2001 4:34 AM
> To: pgsql-hackers(at)postgresql(dot)org
> Subject: Row Versioning, for jdbc updateable result sets
>
> In order to be able to implement updateable result sets there needs to be
> a mechanism for determining if the underlying data has changed since the
> resultset was fetched. Short of retrieving the current data and comparing
> the entire row, can anyone think of a way possibly using the row version
> to determine if the data has been concurrently changed?
>
> Dave

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dale Johnson 2001-06-15 09:58:18 Re: Re: REPLACE INTO table a la mySQL
Previous Message Alex Pilosov 2001-06-15 04:35:13 Re: [PATCH] indexability of << operator for inet/cidr