Skip site navigation (1) Skip section navigation (2)

Re: CURSOR after hitting end

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: pgman(at)candle(dot)pha(dot)pa(dot)us
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: CURSOR after hitting end
Date: 2000-04-05 00:16:48
Message-ID: 20000405091648W.t-ishii@sra.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > > We have this in the CURSOR documentation:
> > >        Once  all  rows  are  fetched,  every  other  fetch access
> > >        returns no rows.
> > 
> > > Is this still true?
> > 
> > Not if you then move or fetch backwards, I should think...
> 
> No, it works.  I think Tatsuo fixed it.  After a FETCH ALL, I did this,
			 ~~~~~~must be Hiroshi...
> and it worked:
--
Tatsuo Ishii

In response to

pgsql-hackers by date

Next:From: Ryan KirkpatrickDate: 2000-04-05 00:32:48
Subject: Linux/Alpha and Postgres 7.0 Beta Status
Previous:From: Tatsuo IshiiDate: 2000-04-05 00:16:32
Subject: Re: Re: BSD/OS regression on 7.0

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group