fix homing_instances table create 25/74425/2
authorEric Multanen <eric.w.multanen@intel.com>
Sat, 8 Dec 2018 08:04:54 +0000 (00:04 -0800)
committerEric Multanen <eric.w.multanen@intel.com>
Tue, 11 Dec 2018 02:07:01 +0000 (18:07 -0800)
specify the catalogdb in the script to
create the homing_instances table.

Renamed file to begin with 'V' instead of 'v'
Not sure if that matters or not.

Change-Id: I35533ae5e22c23b8c1817fe8c373e40fa434f873
Issue-ID: SO-1306
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
adapters/mso-catalog-db-adapter/src/main/resources/db/migration/V4.21__AddHomingTables.sql [moved from adapters/mso-catalog-db-adapter/src/main/resources/db/migration/v4.21_AddHomingTables.sql with 92% similarity]

@@ -1,7 +1,9 @@
+use catalogdb;
+
 CREATE TABLE IF NOT EXISTS `homing_instances` (
 `SERVICE_INSTANCE_ID` varchar(50) NOT NULL,
 `CLOUD_OWNER` VARCHAR(200) NOT NULL,
 `CLOUD_REGION_ID` VARCHAR(200) NOT NULL,
 `OOF_DIRECTIVES` longtext NULL DEFAULT NULL,
 PRIMARY KEY (`SERVICE_INSTANCE_ID`)
-) ;
\ No newline at end of file
+) ;