Re: Proposal: generate_iterator functions

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: generate_iterator functions
Date: 2007-10-18 18:49:21
Message-ID: b42b73150710181149s1bb8841cx24de3af8af398641@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/18/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
> > There was a very similar proposal a little while back (google:
> > array_to_set). I think I like those names better since you are
> > returning a set, not an iterator :-).
>
> I agree, this is a very poor choice of name. There should be some
> reference to arrays in it, for one thing.
>
> generate_array_subscripts() maybe?

array_to_set or array_expand seem a little better imo (shorter, and
symmetry with array_accum()), unless you want to differentiate between
internal funcs (array_cat and the like) vs. user funcs.

I would prefer a proper C implementation to a solution based around
generate_series(). I'm doing a lot of C funcs lately and would be
happy taking a stab at this...

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-10-18 19:08:51 Re: Proposal: generate_iterator functions
Previous Message Heikki Linnakangas 2007-10-18 17:45:02 Re: max_prepared_transactions default ... why 5?