Enhancement: Add support for ?any? column types (e.g. json) #48
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
Ninos
force-pushed
the
support-any-column-types
branch
from
17d7030 to
edcca35
Compare
Ninos
force-pushed
the
support-any-column-types
branch
from
edcca35 to
c96efed
Compare
Small hardening because of the encrypt->decrypt->encrypt (raw) part.... If already string, skip converting value to database value
|
Thankyou for the pull request. I will look to do this in V4 over the next week or two. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Covert values before/after encryption/decrytion by using doctrine internal converter.
PS: I've tested it with json as field, should also work with all others (object, array, simple_array, ...)