Updating sequences in db migration script

Added a dynamic set value changeset for sequence id
to both changelog 05 and 10.

Issue-ID: CPS-900
Change-Id: Ia3ec0b66a89b151435acfa4ebaed3886307b75ea
Signed-off-by: DylanB95EST <dylan.byrne@est.tech>

diff --git a/cps-ri/src/main/resources/changelog/db/changes/05-loadData-fragment.yaml b/cps-ri/src/main/resources/changelog/db/changes/05-loadData-fragment.yaml
index d1125f8..bd95a00 100644 (file)
--- a/cps-ri/src/main/resources/changelog/db/changes/05-loadData-fragment.yaml
+++ b/cps-ri/src/main/resources/changelog/db/changes/05-loadData-fragment.yaml
@@ -1,5 +1,5 @@
 #  ============LICENSE_START=======================================================
-#  Copyright (C) 2021 Nordix Foundation
+#  Copyright (C) 2021-2022 Nordix Foundation
 #  Modifications Copyright (C) 2021 Pantheon.tech
 #  ================================================================================
 #  Licensed under the Apache License, Version 2.0 (the "License");
@@ -69,3 +69,16 @@ databaseChangeLog:
             comment: Fixes the id sequence after data insert with predefined ids
             dbms: postgresql
             sql: ALTER SEQUENCE IF EXISTS fragment_id_seq RESTART WITH 200
+
+  - changeSet:
+      author: cps
+      label: dmi-registry-schema-preload
+      id: 5.2
+      changes:
+        - sql:
+            comment: Sets sequence value to current max value of the ID from the fragment table
+            dbms: postgresql
+            sql: SELECT setval('fragment_id_seq', (SELECT MAX(ID) FROM fragment))
+      rollback:
+        sql: SELECT setval('fragment_id_seq', 200)
+        comment: Rollback Sequence to restart with the sequence number in the last changeset
\ No newline at end of file

diff --git a/cps-ri/src/main/resources/changelog/db/changes/10-loadData-dmi-registry-fragment.yaml b/cps-ri/src/main/resources/changelog/db/changes/10-loadData-dmi-registry-fragment.yaml
index 068a615..b78c920 100644 (file)
--- a/cps-ri/src/main/resources/changelog/db/changes/10-loadData-dmi-registry-fragment.yaml
+++ b/cps-ri/src/main/resources/changelog/db/changes/10-loadData-dmi-registry-fragment.yaml
@@ -74,3 +74,15 @@ databaseChangeLog:
       rollback:
         comment: Rollback for 10.1 is not supported. Please rollback change set 10 to undo change set 10.1. Cannot revert sequence altering.
 
+  - changeSet:
+      author: cps
+      label: dmi-registry-schema-preload
+      id: 10.2
+      changes:
+        - sql:
+            comment: Sets sequence value to current max value of the ID from the fragment table
+            dbms: postgresql
+            sql: SELECT setval('fragment_id_seq', (SELECT MAX(ID) FROM fragment))
+      rollback:
+        sql: SELECT setval('fragment_id_seq', 200)
+        comment: Rollback Sequence to restart with the sequence number in the last changeset
\ No newline at end of file