Merged in SCALE-6-set-db-schema-name (pull request #32)
51b8cb1·Author: Dave Chevell·Closed by: Dave Chevell·2019-11-18
Description
As per https://jira.atlassian.com/browse/SCALE-6, we’re setting <schema-name> to public even when that value isn’t appropriate. This introduces the ability to override the schema name via an additional env variable, and provides sane defaults for backwards compatibility.
Might be nice to take this same approach to selecting the DB driver, since we can remove one required property in a way that will still be backwards compatible/user configurable.
As per https://jira.atlassian.com/browse/SCALE-6, we’re setting <schema-name> to
publiceven when that value isn’t appropriate. This introduces the ability to override the schema name via an additional env variable, and provides sane defaults for backwards compatibility.Might be nice to take this same approach to selecting the DB driver, since we can remove one required property in a way that will still be backwards compatible/user configurable.