Re: UUID v7
От | Andrey Borodin |
---|---|
Тема | Re: UUID v7 |
Дата | |
Msg-id | CAC4A2C8-C115-4EE0-8405-59BEB36418C6@yandex-team.ru обсуждение исходный текст |
Ответ на | Re: UUID v7 (Junwang Zhao <zhjwpku@gmail.com>) |
Ответы |
Re: UUID v7
|
Список | pgsql-hackers |
> On 27 Nov 2024, at 04:11, Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > On Tue, Nov 26, 2024 at 1:55 PM Jelte Fennema-Nio <postgres@jeltef.nl> wrote: >> >> On Tue, 26 Nov 2024 at 21:48, Sergey Prokhorenko >> <sergeyprokhorenko@yahoo.com.au> wrote: >>> gen_uuidv7() is OK >> >> I'd very much prefer to not have a gen_ or get_ prefix as argued before[1][2]. >> >> My vote is still for simply uuidv7() and uuidv4() >> >>> uuid-ossp is outdated, slow and not supported by the author. UUIDv7 is the renaissance of UUIDs. So we should not dependon legacy technology names >> >> agreed >> > > It seems that we agreed to use 'uuidv7' instead of 'uuid_v7()'. There > is discussion whether we should add 'gen_' or 'get_' but let's go back > to the previously-agreed function name 'uuidv7()' for now. We can > rename it later if we find a better name. I think uuidv7() is kind of consensual. > I've attached the new version patch that incorporated all comments and > renamed the functions. Also I avoided using 'if defined(__darwin__) || > defined(_MSC_VER)' twice. Good, I think now it's a bit easier to understand those 2 bits. Thanks! Best regards, Andrey Borodin.
В списке pgsql-hackers по дате отправления: