RE: Row Versioning, for jdbc updateable result sets
Henshall, Stuart - WCP <shenshall@westcountrypublications.co.uk>
From: "Henshall, Stuart - WCP" <SHenshall@westcountrypublications.co.uk>
To: "'Dave Cramer'" <dave@fastcrypt.com>
Cc: pgsql-hackers@postgresql.org
Date: 2001-06-15T09:41:37Z
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@fastcrypt.com] > Sent: Thursday, June 14, 2001 4:34 AM > To: pgsql-hackers@postgresql.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