On Fri, Apr 24, 2009 at 12:15 PM, Sam Mason <sam@xxxxxxxxxxxxx> wrote:
> On Fri, Apr 24, 2009 at 11:55:48AM -0400, Tom Lane wrote:
>> pavunkumar <pavun.bks@xxxxxxxxx> writes:
>> > create or replace function newd(id integer ) returns void as $$
>> > delete from testing where id=$1;
>>
>> Don't use the same name for a parameter as you use for a table column
>> referenced in the function.
>
> I've found it helps to have a standard naming convention here; I only
> use identifiers starting with an underscore (i.e. "_") for function
> parameters and local variables. Column names always start with a lower
> case alphabetic letter. Other people will obviously have different ways
> of dealing with the ambiguity, but this has worked well for me so far.
I absolutely think this ('_' prefix) is the way to go. I make some
exceptions for locals, like n for number, etc. Some people argue for
using in_variable notation, but why use three characters when one is
good enough?
OTOH, I don't camel case columns. Can't please everyone... :-) Also,
to the OP, I'd really advise against naming columns 'id'...it creates
a mess. If you have a table foo, name column 'foo_id'. Less name
conflicts, cleaner queries.
merlin
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
