Skip site navigation (1) Skip section navigation (2)

functional call named notation clashes with SQL feature

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: functional call named notation clashes with SQL feature
Date: 2010-05-26 20:44:30
Message-ID: 1274906670.19408.22.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-hackers
It turns out that the SQL standard uses the function call notation

foo(this AS that)

for something else:

<routine invocation> ::= <routine name> <SQL argument list>

<routine name> ::= [ <schema name> <period> ] <qualified identifier>

<SQL argument list> ::= <left paren> [ <SQL argument> [ { <comma> <SQL
argument> }... ] ] <right paren>

<SQL argument> ::= <value expression>
| <generalized expression>
| <target specification>

<generalized expression> ::= <value expression> AS <path-resolved
user-defined type name>

In systems that have inheritance of composite types, this is used to
specify which type the value is supposed to be interpreted as (for
example, to treat the value as a supertype).

Seems kind of bad to overload this with something completely different.
What should we do?



Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2010-05-26 20:45:10
Subject: Re: Exposing the Xact commit order to the user
Previous:From: Jan WieckDate: 2010-05-26 20:36:43
Subject: Re: Exposing the Xact commit order to the user

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group