Re: latest hstore patch - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: latest hstore patch
Date
Msg-id 874oqle47a.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: latest hstore patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: latest hstore patch
Re: latest hstore patch
List pgsql-hackers
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
David> * More name stuff: Why `hstore_to_list` rather thanDavid> `hstore_to_array`?  And I'm not sure about
`hstore_to_matrix`David>for the 2-dimensional array.  I guess that's better thanDavid>
`hstore_to_multidimensional_array`would be. ;-)
 
>> I intentionally avoided hstore_to_array because it would be>> unclear which one it meant (the 1-d or 2-d result).
Tom> hstore_to_list seems like a pretty horrible name though forTom> something that produces an array.  I also note
that"array"Tom> means "1-D array" according to no less an authority than the SQLTom> standard ;-).  I think we could
livewith hstore_to_array andTom> hstore_to_matrix.  Thoughts, other ideas?
 

I don't feel particularly strongly about the name (I've also
intentionally held off on updating the pgfoundry version of the code
until this is settled so no-one else should care either).

My own expectation is that the operator should normally be used in
preference (though obviously people's tastes will vary in this
respect).

-- 
Andrew (irc:RhodiumToad)


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: latest hstore patch
Next
From: Josh Berkus
Date:
Subject: Re: latest hstore patch