Re: Composite Types and Function Parameters

From: Greg <grigorey(at)yahoo(dot)co(dot)uk>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Composite Types and Function Parameters
Date: 2010-10-26 08:24:54
Message-ID: 551529.46751.qm@web29713.mail.ird.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Merlin, I completely forgot about hstore! I'll give it a go. Thanks!

________________________________
From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Greg <grigorey(at)yahoo(dot)co(dot)uk>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>; pgsql-hackers(at)postgresql(dot)org
Sent: Mon, 25 October, 2010 23:52:55
Subject: Re: [HACKERS] Composite Types and Function Parameters

On Mon, Oct 25, 2010 at 6:38 PM, Greg <grigorey(at)yahoo(dot)co(dot)uk> wrote:
>
> Hi Pavel, thanks! Yeah, thats what I though. I have to have a custom type or a
>very ugly looking solution for passing the params then.
>
> To Postgre dev. team: If anyone who involved in Postgre development reading
>this, just a feature suggestion: allow array that can accept combination of any
>data types to be passed to a function, for example:
> // declare
> create function TEST ( anytypearray[] ) ...
> // calling
> perform TEST (array[bool, int, etc.] ) ....
> This would make such a nice adition to the development for postgre. Although
>this may be complecated to achieve.

probably hstore would be more appropriate for something like that.
You can also declare functions taking composite arrays, anyarray,
variadic array, and variadic "any", although the latter requires
function implementation in C to get the most out of it.

merlin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Itagaki Takahiro 2010-10-26 09:23:37 Re: Extensible executor nodes for preparation of SQL/MED
Previous Message Dean Rasheed 2010-10-26 07:02:22 Re: add label to enum syntax