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

Re: Bug in move 0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, jutso(at)tpts5(dot)seed(dot)net(dot)tw, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug in move 0
Date: 2000-06-11 05:01:00
Message-ID: 8612.960699660@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> We may have documented the behavior, but that doesn't make it right ;-)
>> If someone were to submit a patch to change MOVE 0 into a no-op
>> (without breaking MOVE ALL of course), I'd vote to apply it.

> If we do that, how does one move to the end of a cursor?

MOVE ALL.

The problem right now is just that MOVE ALL is internally represented
as MOVE 0 ... there needs to be a different representation for it.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2000-06-12 01:11:37
Subject: Re: Bug in move 0
Previous:From: Bruce MomjianDate: 2000-06-11 03:56:59
Subject: Re: Bug in move 0

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