RE: Row Versioning, for jdbc updateable result sets
| От | Henshall, Stuart - WCP |
|---|---|
| Тема | RE: Row Versioning, for jdbc updateable result sets |
| Дата | |
| Msg-id | E2870D8CE1CCD311BAF50008C71EDE8E01F745EC@MAIL_EXCHANGE обсуждение исходный текст |
| Ответ на | Row Versioning, for jdbc updateable result sets ("Dave Cramer" <dave@fastcrypt.com>) |
| Список | 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
В списке pgsql-hackers по дате отправления: