From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
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:31:51 |
Message-ID: | 107803A5-10CA-4FBD-A5A3-ABEC3826EC22@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Florents Tselai | 2025-03-10 12:43:15 | Re: encode/decode support for base64url |
Previous Message | Kirill Reshke | 2025-03-10 12:30:23 | Re: Extensible storage manager API - SMGR hook Redux |