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

Re: functional call named notation clashes with SQL feature

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: functional call named notation clashes with SQL feature
Date: 2010-05-28 16:45:44
Message-ID: 4BFFF338.9090902@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> Josh Berkus wrote:
>   
>> Since former SQL Server / Sybase apps are the most likely to use named 
>> parameter notation in PostgreSQL, having a syntax which could be ported 
>> using only "sed" would be nice.
>>
>> Relevant to the whole discussion, though ... is the conflicting SQL 
>> standard syntax something we're every likely to implement?
>>     
>
> Not sure, but I assume people could be using the AS syntax in other
> databases (for the inheritance usage) and then trying to use it in our
> database.
>
>   

Yeah. Whether or not we ever implement it really doesn't matter, IMO. We 
should not be in the business of taking an SQL standard piece of syntax 
and using it for some other purpose.

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: alvherreDate: 2010-05-28 17:05:34
Subject: Re: How to pass around collation information
Previous:From: Bruce MomjianDate: 2010-05-28 16:39:47
Subject: Re: functional call named notation clashes with SQL feature

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