Hi all,
it seems we are quite on the same page: UUIDs are good for Syncope, for
various reasons; side note: I haven't thought before how this will also
simplify the export / import of configuration as XML, not having to deal
any more with OPENJPA_SEQUENCES...
About the doubts expressed:
*
I'd also prefer UUIDs over the current primary keys.
However, that would make migrations from 1.2.x to 2.0 even more
difficult than they probably already will be
- especially if someone uses the Syncope user id outside of Syncope.
Cheers,
Guido
Am 04.04.2016 um 15:51 schrieb Colm O
+1 if it is feasible for 2.0.0. Having a unique global Id maps nicely to
the SCIM Id which "MUST be unique across the SCIM service provider's entire
set of resources.".
Colm.
On Mon, Apr 4, 2016 at 11:11 AM, Massimiliano Perrone <
massimiliano.perr...@tirasa.net> wrote:
>
>
> Il 04/04/2016
Il 04/04/2016 10:23, Francesco Chicchiriccò ha scritto:
Hi all,
a recent e-mail on user@ [1] (about SCIM) made me reconsider one of
the choices we've made in Syncope since the beginning, e.g. using
table generators for long primary keys in several entities, and
especially for users, groups
On 04/04/2016 10:23, Francesco Chicchiriccò wrote:
Hi all,
a recent e-mail on user@ [1] (about SCIM) made me reconsider one of
the choices we've made in Syncope since the beginning, e.g. using
table generators for long primary keys in several entities, and
especially for users, groups and any
Hi all,
a recent e-mail on user@ [1] (about SCIM) made me reconsider one of the
choices we've made in Syncope since the beginning, e.g. using table
generators for long primary keys in several entities, and especially for
users, groups and any objects (and maybe related as attributes,
