Deprecate uid type

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Deprecate uid type

bserdar
Now that we are adding value generators, I believe we should deprecate uid datatype. It is causing a lot of confusion especially when used as a reference. An uid type entity identity is useful to generate the unique IDs, but when that entity is referenced from another entity, the reference type cannot be uid, because uid types are initialized when they are not present. With an uid reference, if the referenced entity is not present, we initialize the reference field with a unique value, creating a dangling reference.

Instead, we should change all uid types to string, and use value generators (uidgenerator) to initialize them.
Reply | Threaded
Open this post in threaded view
|

Re: Deprecate uid type

jewzaam
Administrator
+1

On Fri, Aug 21, 2015 at 9:29 AM bserdar [via lightblue-dev] <[hidden email]> wrote:
Now that we are adding value generators, I believe we should deprecate uid datatype. It is causing a lot of confusion especially when used as a reference. An uid type entity identity is useful to generate the unique IDs, but when that entity is referenced from another entity, the reference type cannot be uid, because uid types are initialized when they are not present. With an uid reference, if the referenced entity is not present, we initialize the reference field with a unique value, creating a dangling reference.

Instead, we should change all uid types to string, and use value generators (uidgenerator) to initialize them.


If you reply to this email, your message will be added to the discussion below:
http://dev.forum.lightblue.io/Deprecate-uid-type-tp384.html
To start a new topic under lightblue-dev, email [hidden email]
To unsubscribe from lightblue-dev, click here.
NAML