the sliver table in gmoc-db2 has unique key uuid, where the unique key should be name

[chaos@bbn.com]

The sliver table in gmoc-db2 is:

CREATE TABLE `sliver` (
  `sliver_id` int(11) NOT NULL auto_increment,
  `uuid` varchar(128) default NULL,
  `name` varchar(128) NOT NULL,
  `last_update` int(10) NOT NULL,
  PRIMARY KEY  (`sliver_id`),
  UNIQUE KEY `uuid` (`uuid`)

However, uuids are not globally unique --- they're only unique at a given entity (aggregate in this case). The name field here contains a sliver URN, which is required to be unique over time at a given aggregate (the expectation is that aggregates implement this by embedding a UUID in the URN, but the requirement doesn't specify an implementation).

The sliver table should use name as a unique key rather than uuid, because names will be globally unique and uuids will not.

[chaos@bbn.com]

The table has been changed. I want to see a new sliver added before i close this, and am blocked on 105 for testing that.

[chaos@bbn.com]

Here's that sliver i tried submitting:

• Sliver entry:

  (53,'87aad770-02c2-4bd3-a5fe-b42d17aed498','urn:publicid:IDN+pgeni.gpolab.bbn.
  com+slice+ecgtest10:87aad770-02c2-4bd3-a5fe-b42d17aed498',1349215369)
  

• Sliver instantiation entry:

  (53,-1,487982,1349229787,1349308542,197,2645,33,6,'1')
  

• Corresponding slice entry:

  (2645,'urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+ecgtest10',1349215340,'c41aa97e-0cc2-11e2-8a62-000c29cca98b',1349222142,1349312142,'chaos@bbn.com'),
  

Based on the submission timestamps, i think that's a match. Closing this.