Use mysql by default in Drupal importers.#347
Merged
jekyllbot merged 1 commit intojekyll:masterfrom Mar 2, 2018
Merged
Conversation
pathawks
approved these changes
Mar 2, 2018
Member
|
@jekyllbot: 🚢 +bug |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#331 added support for PostgreSQL in the Drupal importers. According to the documentation, MySQL is supposed to be the default engine, but the
engineparameter is now mandatory because the default value is not used. This PR fixes that by using the value that was added to theDEFAULTShash./cc @kesara