Re: [PATCH] Add function to_oct
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: John Naylor <john.naylor@enterprisedb.com>, Kirk Wolak <wolakk@gmail.com>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Eric Radman <ericshane@eradman.com>, pgsql-hackers@postgresql.org
Date: 2023-08-21T19:15:28Z
Lists: pgsql-hackers
Attachments
- v9-0001-add-to_bin-and-to_oct.patch (text/x-diff)
On Mon, Aug 21, 2023 at 09:31:37AM +0100, Dean Rasheed wrote: > Hmm, I think just including the doc text update, without the examples > of positive and negative inputs, might not be sufficient to make the > meaning clear to everyone. I added some examples for negative inputs. > Something else that bothers me slightly is the function naming -- > "hexadecimal" gets abbreviated to "hex", "octal" gets abbreviated to > "oct", but "binary" is left as-is. I think it ought to be "to_bin()" > on consistency grounds, even though I understand the words "to bin" > could be interpreted differently. (Looking elsewhere for precedents, > Python has bin(), oct() and hex() functions.) I renamed it to to_bin(). > Also, I think the convention is to always list functions > alphabetically, so to_oct() should really come after to_hex(). I reordered the functions in the docs. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
Commits
-
Add to_bin() and to_oct().
- 260a1f18dae8 17.0 landed