Add JSON Column Type #91
Open
Conversation
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
Conflicts: src/fields/PreparseFieldType.php
Author
|
bump. Any interest in this? |
Owner
|
Yes, very interested, just haven't had any time lately to review and accept the PR - give me a month or so and I'll get it merged! Thanks for your patience 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This adds a native JSON column type. The nice thing about this is you can use Preparse to cache an arbitrary amount of data in to a JSON field and then have MySQL generated columns index on whatever keys you'd like out of that JSON. We're using this liberally to bubble some deeply nested relationships up to a grandparent so we can index/search/sort on it more easily.
/ht @pixleight for the work on this!
/note This is an updated PR from #90, which had some conflicts. This resolves those conflicts.