| 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-28 06:11:43 |
| Message-ID: | 3E83E79F.2FD7844F@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> Hiroshi Inoue wrote:
> > Bruce Momjian wrote:
> > >
> > > Peter Eisentraut wrote:
> > > > Bruce Momjian writes:
> > > >
> >
> > I don't understand what you two are discussing.
> > What's is SENSITIVE, INSENSITIVE or ASESNSITIVE ?
>
> In SQL99 standard, I see:
>
> - If the cursor is insensitive, then significant changes are not
> visible.
>
> - If the cursor is sensitive, then significant changes are
> visible.
>
> - If the cursor is asensitive, then the visibility of significant
> changes is implementation-dependent.
While a cursor is open, another application inserted a
row which satisfies the condition to be contained in
the cursor and committed. Then
If the cursor is SENSITIVE, must it see the row ?
If the cursor is INSENSITIVE, it mustn't see the row ?
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Yarra | 2003-03-28 06:49:04 | Re: ECPG thread-safety |
| Previous Message | Lincoln Yeoh | 2003-03-28 05:37:36 | Re: Solution to UPDATE...INSERT problem |