Re: Warning for undefined cursor

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Warning for undefined cursor
Date: 2003-07-30 21:59:58
Message-ID: 200307302159.h6ULxwq14354@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Peter, you have brought up some good items recently. Are you going to
handle them or do you want them added to the TODO list or 7.4 open items
list.

---------------------------------------------------------------------------

Peter Eisentraut wrote:
> In backend/commands/portalcmds.c we have
>
> /* FIXME: shouldn't this be an ERROR? */
> ereport(WARNING,
> (errcode(ERRCODE_UNDEFINED_CURSOR),
> errmsg("portal \"%s\" does not exist", stmt->portalname)));
>
> The effect of this is that you can fetch from an undefined cursor and
> (successfully) get zero rows plus this warning. I propose that we change
> this to an error. Does anyone see a reason against this, except possibly
> bugward compatibility?
>
> --
> Peter Eisentraut peter_e(at)gmx(dot)net
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-07-30 22:22:55 Re: [PATCHES] [PATCH] Re: Why READ ONLY transactions?
Previous Message Bruce Momjian 2003-07-30 21:41:56 Re: Some macros for error field codes