X-Original-To: pgsql-sql-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id E15DE9FA357 for ; Mon, 3 Jul 2006 12:38:05 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 15443-03 for ; Mon, 3 Jul 2006 12:37:56 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0FA889FA232 for ; Mon, 3 Jul 2006 12:37:55 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k63FbsEj003435; Mon, 3 Jul 2006 11:37:54 -0400 (EDT) To: "Daniel Caune" cc: pgsql-sql@postgresql.org Subject: Re: Local variable and column name conflict In-reply-to: <1E293D3FF63A3740B10AD5AAD88535D2029164E4@UBIMAIL1.ubisoft.org> References: <1E293D3FF63A3740B10AD5AAD88535D2029164E4@UBIMAIL1.ubisoft.org> Comments: In-reply-to "Daniel Caune" message dated "Mon, 03 Jul 2006 11:34:36 -0400" Date: Mon, 03 Jul 2006 11:37:54 -0400 Message-ID: <3434.1151941074@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/31 X-Sequence-Number: 25605 "Daniel Caune" writes: > CREATE OR REPLACE FUNCTION foo(i IN int) > RETURNS void > AS $$ > BEGIN > UPDATE bar > SET i = i; // column i = parameter i > END; > $$ LANGUAGE PLPGSQL; In SELECTs you can qualify the column, ie, bar.i vs i. That doesn't work for an UPDATE target, though, so probably the best answer is "don't do that". I think it's entirely too error-prone anyway ... regards, tom lane