That worked! Thanks Marcus. Earlier, I faced issues with my ‘alter table’ syntax during docker-compose, so I did try building mysql db without the alter table query, and just the updated ‘CREATE TABLE STORAGE_PREFERENCE’ query with the new ‘userStorageQuota’ entry. Since I deleted the mysql image and database-data folder, shouldn’t the new database image contain the ‘userStorageQuota’ entry? The exception I posted earlier was when the code had no alter table query and just the updated ‘CREATE TABLE STORAGE_PREFERENCE’ query. Is my understanding right? Any idea what mistake I might be doing?
Most of my changes to the ‘.sql’ scripts were made through trial and error and workspace searches so I would like to get a better understanding on how the database is built. For instance, 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’? It would be really helpful if you can point me towards some documentation if any. Regards, Vivek. From: "Christie, Marcus Aaron" <[email protected]> Reply-To: <[email protected]> Date: Tuesday, June 16, 2020 at 5:45 PM To: Airavata Dev <[email protected]> Subject: Re: GSoC Milestone 1 update Hi Vivek, https://github.com/apache/airavata/pull/254/files#diff-0d0ad3e35c91564651a24674c1a99411R20 Try removing "IF NOT EXISTS". That syntax works for MariaDB but not MySQL, which the ide-integration docker-compose uses. (An aside, I am updating ide-integration to start up a MariaDB container instead, but that code is still on a branch.) On Jun 14, 2020, at 11:26 PM, Bandaru, Vivek Shresta <[email protected]<mailto:[email protected]>> wrote: I’ve made sure to delete the existing mysql image and ide-integration/database-data folder before building a new mysql image with the new changes, but the schema still won’t change. I encountered the below mentioned exception stacktrace during server startup.
