Closed dyg2104MD closed 8 years ago
For the blueprint_health app, running bundle exec rake config creates a database.yml file like the following:
development: adapter: mysql2 database: blueprintservice_development username: root password: host: localhost pool: 5 timeout: 5000 encoding: utf8 variables: storage_engine: InnoDB
However, storage_engine is a deprecated variable in mysql 5.6 (http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_storage_engine). Using the deprecated variable causes bundle exec rake db:create to fail. Instead it should be default_storage_engine.
I'm looking into if changing this would break backwards compatibility.
@smyers i found the source of the problem I was having with blueprint_health. a description is listed above.
closing this issue. i realized the problem is in the blueprint_service app. not in dice_bag.
For the blueprint_health app, running bundle exec rake config creates a database.yml file like the following:
development: adapter: mysql2 database: blueprintservice_development username: root password: host: localhost pool: 5 timeout: 5000 encoding: utf8 variables: storage_engine: InnoDB
However, storage_engine is a deprecated variable in mysql 5.6 (http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_storage_engine). Using the deprecated variable causes bundle exec rake db:create to fail. Instead it should be default_storage_engine.
I'm looking into if changing this would break backwards compatibility.