Content
View differences
Updated by Carsten Klein over 9 years ago
Considering the given approach, where well known ids of built in roles are hard coded in the source, the approach is destined to fail if future plugins decide to add new built in roles to the system as they compete against each other and also with the open project source for free/available well known built in ids.
It would be best to make the attribute of the Role relation a string that holds UUIDs.
That way, no two plugins nor open project itself, will ever have to compete against each other on the availability and uniqueness of well known identifiers, or builtin ids.
What do you think?
It would be best to make the attribute of the Role relation a string that holds UUIDs.
That way, no two plugins nor open project itself, will ever have to compete against each other on the availability and uniqueness of well known identifiers, or builtin ids.
What do you think?