Page History

...

This step is only required for certain versions of SHRINE that change the schema of the SHRINE query history database. In cases where the schema changes, Typically there should be migration scripts, but if there aren't, it will be necessary to drop the shrine_query_history database, recreate it, and run the latest database scripts. For examples, consult the following files from the installer: https://open.med.harvard.edu/svn/shrine/releases/1.17.1trunk/code/install/i2b2-1.7/shrine/mysql.sh and https://open.med.harvard.edu/svn/shrine/releases/1.17.1/code/install/i2b2-1.7/shrine/mysql/trunk/code/install/i2b2-1.7/shrine/mysql.sql

Schema Changes in 1.18

SHRINE 1.18 adds a column to the SHRINE_QUERY table, and also creates the HUB_QUERY and HUB_QUERY_RESULT tables.

To upgrade the SHRINE_QUERY table, retrieve the adapter-migrate-schema-to-1.18.sql script and run it:

$ wget https://open.med.harvard.edu/svn/shrine/trunk/code/adapter/src/main/resources/adapter-migrate-schema-to-1.18.sql
 $ mysql -u $SHRINE_MYSQL_USER -p$SHRINE_MYSQL_PASSWORD -D shrine_query_history < adapter-migrate-schema-to-1.18.sql

To create the HUB_QUERY and HUB_QUERY_RESULT tables, download the hub.sql script and run it:

$ wget https://open.med.harvard.edu/svn/shrine/trunk/code/broadcaster-aggregator/src/main/resources/hub.sql
 $ mysql -u $SHRINE_MYSQL_USER -p$SHRINE_MYSQL_PASSWORD -D shrine_query_history < hub.sql

Start SHRINE

The only thing left to do at this point is start SHRINE back up. Simply do the following:

...