I forgot to also mention that the changes affect the ide-integration module: - the README.md I linked to in registry-core explains how to copy migrations into ide-integration module's database init script - the ide-integration README.md now documents the command to apply migrations to the database container [0] - the database container image is now a MariaDB image. Migration scripts are easier with MariaDB because supports IF EXISTS/IF NOT EXISTS. - *-derby.sql and *-mysql.sql and persistence.xml files were removed since, at least in my testing, there were unnecessary. They also have caused some confusion in the past since it's not been clear if these files have to be updated or not.
[0] https://github.com/apache/airavata/blame/develop/modules/ide-integration/README.md#L63 > On Jun 25, 2020, at 5:32 PM, Christie, Marcus Aaron <machr...@iu.edu> wrote: > > Hi All, > > I've recently worked on adding some documentation [0] on how to keep the > database schema scripts and migration scripts up to date. In addition I've > added some Maven commands that will use OpenJPA's MappingTool to > automatically create database schema and/or migration scripts (for Derby and > MariaDB/MySQL). I've merged this to the develop branch now and plan to soon > merge to the master branch as well. > > My hope is that this makes it clear exactly how and where to make database > script changes for the registry databases, and that the entire process is > easier. Please see the linked README when you have a chance and let me know > if you have any questions. > > Also, the Jira issue for this work is AIRAVATA-3326 [1] > > Thanks, > > Marcus > > [0] > https://github.com/apache/airavata/blob/develop/modules/registry/registry-core/README.md > > <https://github.com/apache/airavata/blob/develop/modules/registry/registry-core/README.md> > [1] https://issues.apache.org/jira/browse/AIRAVATA-3326 > <https://issues.apache.org/jira/browse/AIRAVATA-3326> >
smime.p7s
Description: S/MIME cryptographic signature
