Re: BUG #8211: Syntax error when creating index on expression - Mailing list pgsql-bugs

From David Johnston
Subject Re: BUG #8211: Syntax error when creating index on expression
Date
Msg-id 1370453214059-5758040.post@n5.nabble.com
Whole thread Raw
In response to Re: BUG #8211: Syntax error when creating index on expression  (bricklen <bricklen@gmail.com>)
List pgsql-bugs
bricklen wrote
> expression
>
> An expression based on one or more columns of the table. The expression
> usually must be written with surrounding parentheses, as shown in the
> syntax. However, the parentheses can be omitted if the expression has the
> form of a function call.

So in fact the example provided:

CREATE INDEX ON films ((lower(title)));

could be written as:

CREATE INDEX ON films (lower(title));

The example expression has yet one additional pair of "()" that are not
required per the syntax since lower(...) is a function call.  Extra "()"
never hurt I suppose...

I don't see this come up too often on the list but I will agree that it is
unexpected to require the extra set of "()".  An example using an actual
expression with the extra "()" and then the function call example without -
to explicitly show when/why they can be omitted in the examples as well as
in the text - is an idea worth considering.

David J.






--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-8211-Syntax-error-when-creating-index-on-expression-tp5758030p5758040.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

pgsql-bugs by date:

Previous
From: geoff.montee@gmail.com
Date:
Subject: BUG #8212: Feature request: View original value of current_user in function with SECURITY DEFINER set
Next
From: eric-postgresql@soroos.net
Date:
Subject: BUG #8213: Set-valued function error in union