Re: BUG #13771: Clarify length of name for prepared statement and return error.

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Weston Catron <wcatron(at)catrondevelopment(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13771: Clarify length of name for prepared statement and return error.
Date: 2015-11-12 15:31:12
Message-ID: CAKFQuwZwkKtUWVRh-yyXnP593sqyL5SgLn8wYmcLj37KprxqMA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Nov 12, 2015 at 6:47 AM, Weston Catron <
wcatron(at)catrondevelopment(dot)com> wrote:

> David,
>
> Okay thank you very much. I guess I didn’t google hard enough to find that
> (I did google!). Maybe its worth a note in the documentation for the next
> version in the prepared statements section that the statement name is an
> identifier. It also doesn’t mention in the identifiers section that the
> prepared statement name is an example of an identifier. Basically there’s
> no direct or indirect link between the two sections which would make it
> hard to match up the two bits of information. Just my two cents, thanks for
> your help.
>
>
​Prepared statement identifiers are only special because that is where you
ran into the problem. Neither suggestion adds anything except limited
redundancy.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Fujii Masao 2015-11-12 16:44:35 Re: BUG #13741: vacuumdb does not accept valid password
Previous Message adolfo-goncalves.junior 2015-11-12 12:19:07 BUG #13773: BigInt column right padding zero