| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | "Karl O(dot) Pinc" <kop(at)karlpinc(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| 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-08-02 15:00:42 |
| Message-ID: | fb2b00fe-65ae-b5ff-3af1-bc05545b92de@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/2/19 10:32 AM, Karl O. Pinc wrote:
> But I'm not happy with putting any function that works with
> bytea into the binary string section. This would mean moving,
> say, length() out of the regular string section.
I'm not sure why. The bytea section already has an entry for its
length() function.
There are also length() functions for bit, character, lseg, path,
tsvector....
I don't really think of those as "a length() function" that works
on all those types. I think of a variety of types, many of which
offer a length() function.
That seems to be reflected in the way the docs are arranged.
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karl O. Pinc | 2019-08-02 15:09:36 | Re: Patch to document base64 encoding |
| Previous Message | Tom Lane | 2019-08-02 14:44:43 | Re: Patch to document base64 encoding |