Re: Built-in binning functions - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Built-in binning functions
Date
Msg-id CA+U5nM+6ktQJHLimF+APuB38kbSLBkjBPXsTp9BrBS7h-NsXxQ@mail.gmail.com
Whole thread Raw
In response to Re: Built-in binning functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Built-in binning functions
List pgsql-hackers
On 30 August 2014 18:24, Tom Lane <tgl@sss.pgh.pa.us> wrote:

>> 3. I am thinking about name - I don't think so varwidth_bucket is correct
>> -- in relation to name "width_bucket" ... what about "range_bucket" or
>> "scope_bucket" ?
>
> Neither of those seem like improvements from here.  I agree with the
> objections to bin() as well.  bucket() might be all right but it still
> seems a bit too generic.  width_bucket(), which at least shows there's
> a relationship to the standard functions, still seems like the best
> of the suggestions so far.

I'd been mulling that over and agree with objections to bin()

Suggest discretize() as a much more informative name. The other names
will be overlooked by anybody that doesn't already know what to look
for.

Thanks for the polymorphic patch, that sounds good. Sorry, not
reviewed more deeply (still travelling).



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [BUGS] Re: BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns
Next
From: David G Johnston
Date:
Subject: Re: [BUGS] Re: BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns