You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2023/01/10 11:52:00 UTC
[jira] [Resolved] (SYNCOPE-1720) Switch persistence identifiers to UUID version 7
[ https://issues.apache.org/jira/browse/SYNCOPE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò resolved SYNCOPE-1720.
---------------------------------------------
Resolution: Fixed
> Switch persistence identifiers to UUID version 7
> ------------------------------------------------
>
> Key: SYNCOPE-1720
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1720
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Labels: UUID, jpa
> Fix For: 2.1.14, 3.0.1, 4.0.0
>
>
> As pointed out by several resources (for example [this blog post|https://vladmihalcea.com/uuid-database-primary-key/]), UUID version 4 are not particularly suitable as primary key identifiers, mainly because of their [random nature|https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_4_(random)] which can cause issues with B-Tree database indexes.
> As pointed out, a better solution is to use [UUID version 7|https://www.ietf.org/archive/id/draft-peabody-dispatch-new-uuid-format-04.html#name-uuid-version-7], time-based UUID bit layout sourced from the widely implemented and well known Unix Epoch timestamp source.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)