| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Cramer <dave(at)fastcrypt(dot)com> |
| Cc: | "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | AW: RE: Row Versioning, for jdbc updateable result sets |
| Date: | 2001-06-18 08:35:33 |
| Message-ID: | 11C1E6749A55D411A9670001FA68796336832A@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> "Dave Cramer" <dave(at)fastcrypt(dot)com> writes:
> > Can the version # of
> > the row be made available to the client?
>
> There is no "version # of the row" in postgres, unless you
> set up such a
> thing for yourself (which could certainly be done, using triggers).
And in addition there is no row version in SQL in general.
So I have the question whether it is actually intended to solve
updateable result sets with proprietary row versions, or whether
someone implemented it that way to optimize concurrent access for
another db system, that blocks readers ?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2001-06-18 09:43:17 | AW: Call for alpha testing: planner statistics revision s |
| Previous Message | Serguei Mokhov | 2001-06-18 06:15:28 | Re: Doc translation |