Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,12 @@ mosip.min-languages.count=1
mosip.max-languages.count=1

#Property to support version upgrade. Version upgrade includes software upgrade and DB upgrade. During the DB upgrade, the DB scripts execution will be done based on the order of versions mentioned here.
#The name of the backup folder which is created during software upgrade will be used as the previously installed version.
mosip.registration.verion.upgrade.version-mappings={ "1.1.4":{ "dbVersion":"1.1.4", "releaseOrder":1}, "1.1.5":{ "dbVersion":"1.1.5", "releaseOrder":2}, "1.1.5.5-P1":{ "dbVersion":"1.1.5.5", "releaseOrder":3}, "1.2.0.1-B1":{ "dbVersion":"1.2.0.1", "releaseOrder":4, "fullSyncEntities":"DynamicFieldDto"}, "1.2.1-SNAPSHOT":{ "dbVersion":"1.2.1", "releaseOrder":5} }
#While adding a new version here, please make sure that the releaseOrder is incremented sequentially.
#The Manifest-Version in MANIFEST.MF in the backup folder which is created during software upgrade will be used as the previously installed version,
# if nothing is found in the "mosip.reg.services.current.version".
#After each DB migration script execution, the "mosip.reg.services.current.version" in the global-config will be updated to the version to which DB is migrated.
#Note: 1.2.0.1-SNAPSHOT is retained, instead of 1.2.0.1 as the configuration was tagged with "1.2.0.1-SNAPSHOT" keyname during 1.2.0.2 stable release. Change in this keyname will lead to failure in identifying a migrated DB version.
mosip.registration.verion.upgrade.version-mappings={ "1.1.4":{ "dbVersion":"1.1.4", "releaseOrder":1}, "1.1.5":{ "dbVersion":"1.1.5", "releaseOrder":2}, "1.1.5.5-P1":{ "dbVersion":"1.1.5.5", "releaseOrder":3}, "1.2.0.1-SNAPSHOT":{ "dbVersion":"1.2.0.1", "releaseOrder":4, "fullSyncEntities":"DynamicFieldDto"}, "1.2.0.2":{ "dbVersion":"1.2.0.2", "releaseOrder":5}, "1.3.0":{ "dbVersion":"1.3.0", "releaseOrder":6} }
Comment thread
coderabbitai[bot] marked this conversation as resolved.

hibernate.hbm2ddl.auto=none
hibernate.dialect=org.hibernate.dialect.DerbyDialect
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
-- Upgrade script for version 1.2.0.2 - No changes to database
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
-- Rollback script for version 1.2.0.2 - No changes to database

This file was deleted.

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
----- insert / update statements

-- Upgrade script for version 1.3.0
ALTER TABLE "REG"."CA_CERT_STORE" ADD COLUMN "CA_CERT_TYPE" VARCHAR(25);
UPDATE "REG"."GLOBAL_PARAM" set VAL='AES/GCM/NoPadding' WHERE CODE='mosip.kernel.crypto.symmetric-algorithm-name';

MERGE INTO "REG"."GLOBAL_PARAM" gp1 USING "SYSIBM"."SYSDUMMY1" ON gp1.code = 'mosip.kernel.partner.cacertificate.upload.minimumvalidity.month' WHEN NOT MATCHED THEN INSERT VALUES ('mosip.kernel.partner.cacertificate.upload.minimumvalidity.month', 'mosip.kernel.partner.cacertificate.upload.minimumvalidity.month', '1', 'CONFIGURATION', 'eng', true, 'SYSTEM', current timestamp, 'SYSTEM', current timestamp, false, current timestamp);
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
-----

-- Rollback script for version 1.3.0
ALTER TABLE "REG"."CA_CERT_STORE" DROP COLUMN "CA_CERT_TYPE";
UPDATE "REG"."GLOBAL_PARAM" set VAL='AES/GCM/PKCS5Padding' WHERE CODE='mosip.kernel.crypto.symmetric-algorithm-name';

delete from "REG"."GLOBAL_PARAM" where code='mosip.kernel.partner.cacertificate.upload.minimumvalidity.month';
Loading