| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | "Karl O(dot) Pinc" <kop(at)karlpinc(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: Patch to document base64 encoding |
| Date: | 2019-07-30 21:44:49 |
| Message-ID: | alpine.DEB.2.21.1907302338470.31365@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
My 0.02 €
>> It seems entirely crazy that encode() and decode() are no longer in the
>> same section, likewise that convert_from() and convert_to() aren't
>> documented together anymore.
>
> Awkward, yes. But findable if you know what the categories are.
>
> I suppose there could be 3 different categories: those that input
> and output strings, those that input and output binary, and those
> that convert -- inputting one data type and outputting another.
Personnaly, I'd be ok with having a separate "conversion function" table,
and also with Tom suggestion to have string functions with "only simple
string" functions, and if any binary appears it is moved into the binary
section.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2019-07-30 21:55:57 | Re: [Patch] Adding CORRESPONDING/CORRESPONDING BY to set operation |
| Previous Message | 毛瑞嘉 | 2019-07-30 21:43:05 | [Patch] Adding CORRESPONDING/CORRESPONDING BY to set operation |