| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Han <zhouhanok(at)vip(dot)sina(dot)com>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: updateable cursors & visibility |
| Date: | 2003-03-27 09:06:39 |
| Message-ID: | 3E82BF1F.A73087EA@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
Bruce Momjian wrote:
>
> Sorry, no idea. Peter's idea is that FOR UPDATE requires SENSITIVE, so
> INSENSITIVE has to be READONLY because the update has to see other
> changes to be accurate.
>
> I think clearly SENSITIVE/READONLY should be possible, so:
>
> READONLY/SENSITIVE possible
> READONLY/INSENSITIVE possible
> FOR UPDATE/SENSITIVE possible
> FOR UPDATE/INSENSITIVE not possible
>
> READONLY can be either way, while FOR UPDATE requires SENSITIVE.
SENSITIVE doesn't mean *not INSENESITIVE*.
INSENSITIVE doesn't mean *not SENSITIVE*.
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lincoln Yeoh | 2003-03-27 09:19:18 | Re: Solution to UPDATE...INSERT problem |
| Previous Message | Tom Lane | 2003-03-27 07:13:28 | Re: Solution to UPDATE...INSERT problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Giuliano Gavazzi | 2003-03-27 09:14:58 | Re: Compiling with unixodbc support |
| Previous Message | Bruce Momjian | 2003-03-26 16:01:26 | Re: updateable cursors & visibility |