Re: Out parameters handling - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Out parameters handling
Date
Msg-id 49B1D183.5030203@agliodbs.com
Whole thread Raw
In response to Re: Out parameters handling  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Out parameters handling  (Robert Haas <robertmhaas@gmail.com>)
Re: Out parameters handling  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-hackers
Robert,

> I wonder whether it would be possible to make PL/pgsql take :foo to
> mean the parameter named foo, and then provide an option to make that
> THE ONLY WAY to refer to the parameter foo.  For
> backward-compatibility, and compatibility with (ahem) other database
> products, we probably don't want to remove the option to have foo
> mean... any damn thing named foo you can put your hands on.  But it
> would be nice to at least have the option of disabling that behavior
> when compatibility is not an issue, and correctness is.

Thing is, anybody can institute their own naming convention.  I've long 
used v_ as a prefix.  Allowing : would save me some keystrokes, but 
that's about it.

--Josh



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Out parameters handling
Next
From: Andrew Gierth
Date:
Subject: NOT NULL constraint vs. composite type (vs. plpgsql)