Re: BUG #13771: Clarify length of name for prepared statement and return error.
От | David G. Johnston |
---|---|
Тема | Re: BUG #13771: Clarify length of name for prepared statement and return error. |
Дата | |
Msg-id | CAKFQuwY1KmJ0tQuNVhd=GVy4-VQrBVfEaawNxySomBbP7mxRkQ@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #13771: Clarify length of name for prepared statement and return error. (wcatron@catrondevelopment.com) |
Список | pgsql-bugs |
On Wednesday, November 11, 2015, <wcatron@catrondevelopment.com> wrote: > The following bug has been logged on the website: > > Bug reference: 13771 > Logged by: Weston Catron > Email address: wcatron@catrondevelopment.com <javascript:;> > PostgreSQL version: 9.3.3 > Operating system: linux > Description: > > Please clarify in the documentation how long a prepared statement name can > be. I tested it at 63 characters. This was not made clear anywhere and I > was > running into issues where the differences were past the 63 character mark > and it was trying to run queries with the wrong statement. It also only > CLIPED it didn't return an error of any kind. > > > Documented here. http://www.postgresql.org/docs/9.1/static/sql-syntax-lexical.html It applies to all identifiers (e.g., table names, column names, etc...) Why it had to be truncated instead of an error I don't know but at this point backward compatibility is likely going to prevent any change. David J.
В списке pgsql-bugs по дате отправления: