Open paynejd opened 1 year ago
@paynejd uuid
was added to support backword compatibility when we migrated to v2 (MongoDB to Postgres). v1 had 'uuid' (BSON ID via MongoDB) attached to each object, which was replaced by an autoincremented Integer ID in v2 (Postgres pk autoint).
The DB still has the field name as "id", but the API reports it as "uuid". So the impact is much less internally in OCL, they are hardly used anywhere, except a couple of places in TB (not in display, but in code).
@snyaggarwal We need to understand the impact of this change before we pull the trigger
concept.name.uuid
andconcept.description.uuid
are incorrectly named because these are actually local database identifiers, not UUIDs.id
is the correct name for these fields.Can you take a look at the impact that changing these field names would have throughout the api and TB?
Are there other uses of
uuid
in the API information model?