| From: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | 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 12:43:15 |
| Message-ID: | CA+v5N423WDLNVg_VoQGSZqFnH6zATdd483x0+ApuMx0E8xRbnA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 10, 2025, 14:32 Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > On 10 Mar 2025, at 12:28, Florents Tselai <florents(dot)tselai(at)gmail(dot)com>
> wrote:
>
> > Here's a C implementation for this, along with some tests and
> documentation.
> > Tests are copied from cpython's implementation of urlsafe_b64encode and
> urlsafe_b64decode.
>
> + <function>base64url_encode</function> (
> <parameter>input</parameter> <type>bytea</type> )
>
> Shouldn't this be modelled around how base64 works with the encode() and
> decode() functions, ie encode('123\001', 'base64')?
>
> https://www.postgresql.org/docs/devel/functions-binarystring.html
>
> --
> Daniel Gustafsson
>
Oh well - you're probably right.
I guess I was blinded by my convenience.
Adding a 'base64url' option there is more appropriate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirill Reshke | 2025-03-10 13:05:22 | Re: INSERT ... ON CONFLICT DO SELECT [FOR ...] take 2 |
| Previous Message | Daniel Gustafsson | 2025-03-10 12:31:51 | Re: encode/decode support for base64url |