Issue 18137
Nub builds have usage keys from postgres sequence
18137
Reporter: mdoering
Assignee: mdoering
Type: Bug
Summary: Nub builds have usage keys from postgres sequence
Description: Some pro parte usages of a newly build and synced backbone have usage keys above the maximum range and must have been generated by the postgres sequence. All nub usageKeys should have been generated by the IdGenerator of the nub build though with pro parte usage keys being attached to the pro parte neo4j relation as the single neo synonym node becomes multiple usage records in postgres and we need several ids.
Priority: Critical
Resolution: Fixed
Status: Closed
Created: 2016-01-06 21:34:18.667
Updated: 2016-02-11 11:38:23.318
Resolved: 2016-02-11 11:38:09.369
Author: mdoering@gbif.org
Created: 2016-01-06 21:34:38.548
Updated: 2016-01-06 21:36:11.098
uat_checklistbank=> select count(*) from name_usage where id > 99999999 and dataset_key='d7dddbf4-2cf0-4f39-9b2a-bb099caae36c';
count
-------
8770