Re: bug in function arguments "recognition"

From: Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>
To:
Cc: PostgreSQL <pgsql-general(at)postgresql(dot)org>
Subject: Re: bug in function arguments "recognition"
Date: 2010-03-03 15:41:26
Message-ID: 20100303164126.51a18ef3@dawn.webthatworks.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 03 Mar 2010 10:22:31 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> writes:
> > I've a function defined as:
> > create or replace function catalog_relateditems(__itemid bigint,
> > families int[]...
>
> If you want any useful comments, you're going to have to show a
> complete example, rather than selectively editing out what you
> think is irrelevant (and, no doubt, isn't).

Golden rule... I thought that psql auto completion was a good enough
proof something wasn't working and I was thinking if someone could
give me a good advice to trim down the clutter to build up a simpler
function that could misbehave.

I was not aware that in and out parameters could be intermixed and I
was expecting an error, but pg was pretty happy with the syntax and
this was enough to put me astray.

Sorry

--
Ivan Sergio Borgonovo
http://www.webthatworks.it

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Sabino Mullane 2010-03-03 15:46:14 Re: disable triggers isolated to transaction only?
Previous Message Markus Wollny 2010-03-03 15:33:58 Massive table bloat