[
https://issues.apache.org/jira/browse/SYNCOPE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17656608#comment-17656608
]
ASF subversion and git services commented on SYNCOPE-1720:
----------------------------------------------------------
Commit d205dc62aec839a0c9a669f922bb3198ec9552c8 in syncope's branch
refs/heads/3_0_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=d205dc62ae ]
[SYNCOPE-1720] Fixing test execution
> 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)
