Re: Proposal: Trigonometric functions in degrees - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Proposal: Trigonometric functions in degrees
Date
Msg-id CA+TgmoY_x+0xvuqSXerNbp2XSAPfxVY6Bu0=UtY+1MfvkEsf2Q@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: Trigonometric functions in degrees  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Proposal: Trigonometric functions in degrees  (Simon Riggs <simon@2ndQuadrant.com>)
fortnight interval support  (Nathan Wagner <nw+pg@hydaspes.if.org>)
List pgsql-hackers
On Mon, Oct 26, 2015 at 1:29 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On 26 October 2015 at 10:18, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Dean Rasheed <dean.a.rasheed@gmail.com> writes:
>> > On 25 October 2015 at 09:16, Emre Hasegeli <emre@hasegeli.com> wrote:
>> >> I would prefer gradian over degree.
>>
>> > I think gradians are generally less commonly used than degrees and
>> > radians, so I'm less inclined to include them.
>>
>> I agree.  gradians are not often used at all, AFAICT.
>
>
> I've never seen anyone use a gradian, even though my calculator had them
> when I was 16.
>
> I even misread the request, thinking he meant "radians". Definitely -1 to
> gradians in PostgreSQL.
>
> Also -1 to furlongs, fortnights, pecks and hundredweight, amongst others.

Aw, you're no fun.  select '1 fortnight'::interval => '14 days' would be cool.

https://en.wikipedia.org/wiki/FFF_system

I don't think we should be dismissive of gradians, because I'm sure
Emre's request was serious and in good faith, but I don't feel a
crying need for them either.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Proposal: Trigonometric functions in degrees
Next
From: fortin.christian@videotron.ca
Date:
Subject: UTF-32 support in PostgreSQL ?