Two database schema issues 61/41061/2
authorRob Daugherty <rd472p@att.com>
Wed, 4 Apr 2018 19:59:35 +0000 (15:59 -0400)
committerRob Daugherty <rd472p@att.com>
Wed, 4 Apr 2018 20:07:08 +0000 (16:07 -0400)
commit811511f0adb7dd53b0c3404fc40b355fd24a719b
treec0580d73489abc42e1911470347d97b2d20b7100
parentc9b74b470e0090a9451575a2271f05b237a548ea
Two database schema issues

1. The operation_status table is missing the service_name column,
   which was added in the amsterdam release
2. Table camundabpmn.ACT_HI_VARINST has no column STATE_

Change-Id: Ifadfce23a78b9404b677c1a9597003b3c8b9187d
Issue-ID: SO-560
Signed-off-by: Rob Daugherty <rd472p@att.com>
volumes/mariadb/docker-entrypoint-initdb.d/db-sql-scripts/bulkload-files/default/create_mso_db-default.sql
volumes/mariadb/docker-entrypoint-initdb.d/db-sql-scripts/camunda/mariadb_engine_7.8.0-ee.sql [moved from volumes/mariadb/docker-entrypoint-initdb.d/db-sql-scripts/camunda/mariadb_engine_7.7.3-ee.sql with 96% similarity]
volumes/mariadb/docker-entrypoint-initdb.d/db-sql-scripts/main-schemas/MySQL-Requests-schema.sql