Отв.: Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions

From: Sergey Prokhorenko <sergeyprokhorenko(at)yahoo(dot)com(dot)au>
To: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Subject: Отв.: Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions
Date: 2025-10-27 15:33:31
Message-ID: 1244660844.809618.1761579211494@mail.yahoo.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Sergey,

> It seems that bytea is your personal interest, since you continue to impose your bytea when a better solution has already been found with uuid_encode() and uuid_decode().

In the previous messages Masahiko Sawada wrote:

> Or providing
> 'uuid_encode(uuid, format text) -> text' and 'uuid_decode(text, format
> text) -> uuid' might make sense too, but I'm not sure. I'd like to
> hear opinions from other hackers too.

I merely shared my personal opinion on why I think this is a bad idea.
Let's see what other people think.

--
Best regards,
Aleksander Alekseev

_____________________
You didn't give any arguments in favor of your opinion

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2025-10-27 15:33:57 Re: Remove specific \r\n code in TAP for Windows
Previous Message Tomas Vondra 2025-10-27 15:14:38 Re: Optimizing ResouceOwner to speed up COPY