Re: updateable cursors & visibility

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Neil Conway" <neilc(at)samurai(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: updateable cursors & visibility
Date: 2003-03-29 01:03:41
Message-ID: EKEJJICOHDIEMGPNIFIJMEDOLBAA.Inoue@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
>
> Hiroshi Inoue wrote:
> > > > If the cursor is INSENSITIVE, it mustn't see the row ?
> > >
> > > Right.
> >
> > If so, isn't the difference between SENSITIVE and INSENSITIVE extreme ?
>
> Yes.
>
> > Why do you or Peter refer to ASENSITIVE little ?
>
> Not sure --- ASENSITIVE seems to be "do whatever you want", which is
> always good.
>
> > And what does the following mean ? It is placed just before the
> sentences
> > you quoted first.
> >
> > If a cursor is open, and the SQL-transaction in which the cursor was
> > opened makes a significant change to SQL-data, then whether that
> > change is visible through that cursor before it is closed is
> determined
> > as follows:
>
> There seem to be two sections, one dealing with seeing change made by
> the same transaction:

May I ask again ?
Must a SENSITIVE cursor see other applications' changes made
while the cursor is open ?

regards,
Hiroshi Inoue

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-03-29 02:04:17 Re: updateable cursors & visibility
Previous Message Bruce Momjian 2003-03-28 23:33:49 Re: updateable cursors & visibility