Re: Array Parameters in EXECUTE

From: Sim Zacks <sim(at)compulab(dot)co(dot)il>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Array Parameters in EXECUTE
Date: 2009-06-11 17:46:23
Message-ID: h0rfti$1dgh$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

You get what you ask for :-)
You can use the function array-to-string with a comma as the separator.
The array should look like '{val1,val2,val3}' in text format.

Sim

Shakil Shaikh wrote:
> Re added list!
>
> --------------------------------------------------
> Sent: Thursday, June 11, 2009 11:04 AM
> To: "Shakil Shaikh" <>
> Subject: Re: [GENERAL] Array Parameters in EXECUTE
>
>>> Here's my general situation: I have a function which takes in an
>>> optional ARRAY of Ids as so:
>>>
>>> RETURN QUERY SELECT * FROM a WHERE a.id = ANY(v_ids) or v_ids is null;
>>>
>>> However it seems that the ...or v_ids is null... bit forces a sequential
>>
>>
>> If I understand what you are trying to do, if your passed in parameter
>> is null then select * and if there is something there then check it.
>> I would put the statement in an if:
>>
>> if v_ids is null then
>> RETURN QUERY select * from a;
>> else
>> return query SELECT * FROM a WHERE a.id = ANY(v_ids)
>> end if;
>>
>
> This works fine for the trivial case given but not for when there are
> multiple optional array parameters (I know, I know...). I will probably
> use branching for one or two parameters, but for three or four it might
> get a bit cumbersome so I was wondering if there was a more general
> solution.
>
> Shak
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Josh Berkus 2009-06-11 18:13:40 Re: [sfpug] "Rails and PostgreSQL" now up on media.postgresql.org
Previous Message Gus Gutoski 2009-06-11 17:43:43 Re: help with data recovery from injected UPDATE