aboutsummaryrefslogtreecommitdiffstats
path: root/adapters/mso-catalog-db-adapter/src/main/resources/db
diff options
context:
space:
mode:
authorOleg Mitsura <oleg.mitsura@amdocs.com>2021-07-27 16:24:23 -0400
committerOleg Mitsura <oleg.mitsura@amdocs.com>2021-08-26 10:56:05 -0400
commit1a506214e5779e068c1d2b7b34dbf3d1c2e8c637 (patch)
treeebb568c24921793a2998f9d3a180e9e778d97c56 /adapters/mso-catalog-db-adapter/src/main/resources/db
parent7498ebd8f5f866a271379330a17291f06d5fe889 (diff)
SO-3720 BuildingBlockRollback lookup table
Issue-ID: SO-3720 BuildingBlockRollback lookup table will indicate the rollback BB to take; this is the first part for simplifying WorkflowActionBBTasks logic: instead of doing string matching, we just do a lookup of a block to call to perform the rollback operation. In some cases, the Action is set as well - this would be needed for certain BBs, in that case, there is a corresponding rollbackAction as well. Change-Id: I072a2ada894cf4672f5a1cdce762605757cb1d14 Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
Diffstat (limited to 'adapters/mso-catalog-db-adapter/src/main/resources/db')
-rw-r--r--adapters/mso-catalog-db-adapter/src/main/resources/db/migration/V8.9.1__AddBuildingBlockRollback.sql10
1 files changed, 10 insertions, 0 deletions
diff --git a/adapters/mso-catalog-db-adapter/src/main/resources/db/migration/V8.9.1__AddBuildingBlockRollback.sql b/adapters/mso-catalog-db-adapter/src/main/resources/db/migration/V8.9.1__AddBuildingBlockRollback.sql
new file mode 100644
index 0000000000..11dd1ecfb3
--- /dev/null
+++ b/adapters/mso-catalog-db-adapter/src/main/resources/db/migration/V8.9.1__AddBuildingBlockRollback.sql
@@ -0,0 +1,10 @@
+use catalogdb;
+
+CREATE TABLE IF NOT EXISTS `building_block_rollback` (
+ `ID` INT NOT NULL AUTO_INCREMENT,
+ `BUILDING_BLOCK_NAME` varchar(200) NOT NULL,
+ `ACTION` varchar(200) null,
+ `ROLLBACK_BUILDING_BLOCK_NAME` varchar(200) NOT NULL,
+ `ROLLBACK_ACTION` varchar(200) NULL,
+ PRIMARY KEY (`ID`)
+) ENGINE=InnoDB DEFAULT CHARSET=latin1;