Hi Marcus, Thanks again for the detailed explanation. Now the.sql scripts make a lot of sense.
Regards, Vivek. Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Christie, Marcus Aaron <[email protected]> Sent: Thursday, June 18, 2020 12:00 PM To: Airavata Dev Subject: Re: GSoC Milestone 1 update On Jun 17, 2020, at 10:00 PM, Bandaru, Vivek Shresta <[email protected]<mailto:[email protected]>> wrote: 1. I’ve tried building the docker image with ‘CREATE TABLE’ changes in the appcatalog-mysql.sql and appcatalog-derby.sql inregistry/src/main/resources or/and in database-scripts/ but still the schema never changed. Only changes in 01-databases.sql or the release-migration-scripts changed the schema in my case. Where are these files used? Do I need to remove the changes I’ve made in these files? Yeah, like I said appcatalog-mysql.sql etc. would only be used when there are no tables, but ide-integration loads a database dump from the start, so those files never get used in ide-integration. Probably they should be removed from the ide-integration module and you can remove your changes from them. when updating the database schema you need to update: - <database>-mysql.sql in registry-core - <database>-derby.sql in registry-core - MariaDB migration script in release-migration-scripts/next/DeltaScripts/<database>_schema_delta.sql - likewise in ide-integration 0*-<database>-migrations.sql 2.. I’m assuming the folders in the release-migration-scripts represent the mysql version. Is my understanding right? Right. 3. Why do we have almost similar scripts at two places in the codebase? appcatalog_derby.sql and appcatalog_mysql.sql in the folders ‘ide-integration/src/main/resources/database-scripts’ and ‘registry/src/main/resources’? See #1, the duplicates in ide-integration I don't think are needed actually. Maybe Dimuthu can chime in.
