X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 484F49DD744;
	Thu,  8 Dec 2005 14:03:14 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 20738-05; Thu,  8 Dec 2005 14:03:13 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from candle.pha.pa.us (candle.pha.pa.us [64.139.89.126])
	by postgresql.org (Postfix) with ESMTP id 2FE1F9DD735;
	Thu,  8 Dec 2005 14:03:10 -0400 (AST)
Received: (from pgman@localhost)
	by candle.pha.pa.us (8.11.6/8.11.6) id jB8I39M22478;
	Thu, 8 Dec 2005 13:03:09 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200512081803.jB8I39M22478@candle.pha.pa.us>
Subject: Re: [PATCHES] pl/pgSQL doco patch
In-Reply-To: <200511170926.55631.philip@utiba.com>
To: Philip Yarra <philip@utiba.com>
Date: Thu, 8 Dec 2005 13:03:09 -0500 (EST)
CC: Andrew Dunstan <andrew@dunslane.net>, pgsql-patches@postgresql.org,
	pgsql-docs@postgresql.org
X-Mailer: ELM [version 2.4ME+ PL121 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.004 required=5 tests=[AWL=0.004]
X-Spam-Score: 0.004
X-Spam-Level: 
X-Archive-Number: 200512/9
X-Sequence-Number: 3357


I think the Oracle porting section is the correct place for this item. 
Thanks for the patch.

---------------------------------------------------------------------------

Philip Yarra wrote:
> On Thu, 17 Nov 2005 01:40 am, Andrew Dunstan wrote:
> > I am wondering we should make this warning more prominent - it would be
> > easily missed buried on the Oracle porting section, and I have seen
> > people caught by it lots of times.
> 
> I added it to the Oracle section because I found this syntax while porting an 
> Oracle stored proc to a pl/pgSQL function, and assumed it was an Oracle-ism.
> 
> Do other RDBMSs also allow you to qualify function_name.param_name to 
> distinguish a param from a column of the same name? If so, sure, I'll put it 
> somewhere more general (suggestions?), and Tom, I think that would lend 
> weight to allowing PostgreSQL to do it too (not because it's The Right Thing, 
> but for interoperability and ease of porting). Thoughts?
> 
> Regards, Philip.
> 
> -- 
> 
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are,
> by definition, not smart enough to debug it." - Brian W. Kernighan
> 
> -----------------
> Utiba Pty Ltd 
> This message has been scanned for viruses and
> dangerous content by Utiba mail server and is 
> believed to be clean.
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073