Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions]

From: Michael Glaesemann <grzm(at)seespotcode(dot)net>
To: Decibel! <decibel(at)decibel(dot)org>
Cc: Jeremy Drake <pgsql(at)jdrake(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions]
Date: 2007-08-08 17:29:43
Message-ID: 8FE363D9-E3A5-41BB-AD85-9D7CBD817EB1@seespotcode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Aug 8, 2007, at 12:18 , Decibel! wrote:

> On Wed, Aug 08, 2007 at 12:03:34PM -0500, Michael Glaesemann wrote:
>> Personally, I think expandarray is more appropriate and its
>> functionality probably more generally useful, as it identifies the
>> array indices as well. Note you can also rename the columns.
>
> Sure. My point is that we should have a way to convert arrays to sets
> and back in the backend.

Can't really argue with you there, as I find array_accum myself.
(Though I'd still nit-pick that this isn't an array to set
conversion, but rather array to--possibly single-column--table.)

Michael Glaesemann
grzm seespotcode net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2007-08-08 18:00:27 Re: HOT patch, missing things
Previous Message Decibel! 2007-08-08 17:18:44 Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions]