Re: proposal: minscale, rtrim, btrim functions for numeric - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: minscale, rtrim, btrim functions for numeric
Date
Msg-id CAFj8pRChytNyGuWzde1q7gr6gQuCHOUn5Gdak-zKyV9oCRo14w@mail.gmail.com
Whole thread Raw
In response to Re: proposal: minscale, rtrim, btrim functions for numeric  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: proposal: minscale, rtrim, btrim functions for numeric
List pgsql-hackers


so 9. 11. 2019 v 21:34 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal:
Pavel Stehule <pavel.stehule@gmail.com> writes:
> four years ago Marko Tiikkaja send a patch for numeric_trim functions. This
> functions removed ending zeroes from numeric value. This is useful feature,
> but there was not any progress on this patch. I think so this feature can
> be interesting, so I would to revitalize this patch.

> Original discussion
> https://www.postgresql-archive.org/Add-numeric-trim-numeric-td5874444.html

A more useful link is
https://www.postgresql.org/message-id/flat/564D3ADB.7000808%40joh.to
and the earlier discussion is at
https://www.postgresql.org/message-id/flat/5643125E.1030605%40joh.to

Re-reading that thread, I don't really think there's much support for
anything beyond the minscale() function.  The rest are just inviting
confusion with string-related functions.  And I really don't like
establishing a precedent that btrim() and rtrim() are the same.

I have to agree, so using trim, rtrim names is not best. On second hand, probably to most often usage of minscale function will be inside expression round(x, minscale(x)), so this functionality can be in core. A question is a name.

maybe to_minscale(numeric) ?

Regards

Pavel


                        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Handy describe_pg_lock function
Next
From: Amit Kapila
Date:
Subject: Re: First-draft back-branch release notes are up for review