Re: Out parameters handling

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: Asko Oja <ascoja(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Out parameters handling
Date: 2009-03-06 21:49:16
Message-ID: 36e682920903061349u16f87f2dyf79971a6450d5f5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 6, 2009 at 4:29 PM, Asko Oja <ascoja(at)gmail(dot)com> wrote:

> It was one of my worst Friday's finding out that this brain dead
> implementation of out parameters had been part of fuck up again.

:)

>
> This time we did notice it two days too late.
> I wish for a way to use out parameters in functions only through some
> predefined prefix like in triggers new and old. Means i would like to limit
> referencing to out parameters to one prefix only defined in the beginning of
> declare section of stored procedure.
> It really sucks what kind of mistakes you can pass to production
> unknowingly. I would much prefer a way to prevent such nonsense.
> Here was the case where out parameters were with same names with select
> into field names resulting in null outcome. Just yesterday we had similar
> case with update statement.
>

Well, it's a problem with the language not parsing things correctly and
doing, in many cases, brain-dead replacements. I don't know of any
developer using OUT parameters that doesn't run into this problem at one
time or another :(

--
Jonah H. Harris, Senior DBA
myYearbook.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lawrence, Ramon 2009-03-06 22:00:03 Re: Proposed Patch to Improve Performance of Multi-BatchHash Join for Skewed Data Sets
Previous Message Asko Oja 2009-03-06 21:29:13 Out parameters handling