Uploaded image for project: 'Portal'
  1. Portal
  2. POR-3003

Nub builds have usage keys from postgres sequence

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Checklistbank
    • Labels:
      None

      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.

        Gliffy Diagrams

        Issue Links

          Activity

          Hide
          Markus Döring added a comment - - edited

          uat_checklistbank=> select count from name_usage where id > 99999999 and dataset_key='d7dddbf4-2cf0-4f39-9b2a-bb099caae36c';
          count
          -------
          8770

          Show
          Markus Döring added a comment - - edited uat_checklistbank=> select count from name_usage where id > 99999999 and dataset_key='d7dddbf4-2cf0-4f39-9b2a-bb099caae36c'; count ------- 8770
          Show
          Markus Döring added a comment - https://github.com/gbif/checklistbank/commit/37cd65472ae7fb17946ea30344004c0cb6d07eb3#diff-926115b4a85cbe526f04c1696cf679f3R1303

            People

            • Assignee:
              Markus Döring
              Reporter:
              Markus Döring
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: