| From: | Cary Huang <cary(dot)huang(at)highgo(dot)ca> |
|---|---|
| To: | "Florents Tselai" <florents(dot)tselai(at)gmail(dot)com> |
| Cc: | "Daniel Gustafsson" <daniel(at)yesql(dot)se>, "Aleksander Alekseev" <aleksander(at)timescale(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Przemysław Sztoch" <przemyslaw(at)sztoch(dot)pl> |
| Subject: | Re: encode/decode support for base64url |
| Date: | 2025-03-10 22:51:06 |
| Message-ID: | 195824135d0.d85a25ee979515.4810228258675500120@highgo.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Oh well - you're probably right.
> I guess I was blinded by my convenience.
> Adding a 'base64url' option there is more appropriate.
I agree with it too. It is neater to add "base64url" as a new option for
encode() and decode() SQL functions in encode.c.
In addition, you may also want to add the C versions of base64rul encode
and decode functions to "src/common/base64.c" as new API calls so that
the frontend, backend applications and extensions can also have access
to these base64url conversions.
Cary Huang
-------------
HighGo Software Inc. (Canada)
cary(dot)huang(at)highgo(dot)ca
www.highgo.ca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Przemysław Sztoch | 2025-03-10 23:01:26 | Re: encode/decode support for base64url |
| Previous Message | Melanie Plageman | 2025-03-10 22:11:52 | Re: BitmapHeapScan streaming read user and prelim refactoring |