Stringify on save for MySQL #48
Merged
Conversation
This file contains 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
|
Thanks @pandapaul that does it, I'll try to publish a release ASAP. |
|
Awesome. Thanks very much. I'll keep an eye out for it. :) |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
@ricardogama Heya. I finally took the time to have a deeper look into this, and I think this should resolve what we were discussing before in #47. Specifically, I've changed the MySQL support tests to demonstrate failure without use of the plugin and proper functionality with use of it. I saw the difficulty you were referring to with regards to reproducing the problem. It seems as though MySQL accepts arrays on save but not objects.