Re: BUG #13661: Using word LIMIT - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #13661: Using word LIMIT
Date
Msg-id CAKFQuwbpH+qfQknng-CDbJf2j=F0kEAOwsCvOUJZKHect2hR0g@mail.gmail.com
Whole thread Raw
In response to BUG #13661: Using word LIMIT  (kmursk@rambler.ru)
List pgsql-bugs
On Fri, Oct 2, 2015 at 5:32 AM, <kmursk@rambler.ru> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      13661
> Logged by:          Danilenko Andrey
> Email address:      kmursk@rambler.ru
> PostgreSQL version: 9.4.1
> Operating system:   Windows
> Description:
>
> Word LIMIT is a clause of SQL-statement and could not be used as a name o=
f
> column. But it is possible to create table with this column-name. And for
> all that such column-name transforms in upper case. That is bug, because
> there shoud not be possibility to use name LIMIT at all with clause CREAT=
E
> TABLE. And moreover there shoud not be implicit case-transformation
>

As John indicated naming has quite a few rules and dynamics associated with
it.  If you do not provide exactly what you are typing in or viewing it is
hard to provide a targeted response and we end up quoting you the manual
with a few personal embellishments.

Implicit case transformation to all upper-case is indeed unexpected but
lacking a reproducible example it is going to be attributed to user-error
and not a bug.

David J.
=E2=80=8B

pgsql-bugs by date:

Previous
From: Dave Page
Date:
Subject: Re: BUG #13662: Base Directory Slashes are FORWARD
Next
From: Serge
Date:
Subject: Re: BUG #13622: unsafe use of relative rpath libpq.5.dylib