Support latest PG version from will/crystal-pg#232 #220
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
|
Any blocker for this? Clear remains non-functioning for crystal 1.1.1+ without this change. |
|
@anykeyh I would love to see this included too |
|
Just realized you made a PR. Did another one related to this subject. I will go with your PR and merge that tonight on master / generate a new version. Thanks, |
|
Huzzah! Thanks @anykeyh! |
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.
will/crystal-pg#232 - changes default postgres JSON fields from being read as JSON::Any to JSON::PullParser. Updated Clear to support that.
Also updated shards.lock file, though only pg needed to be updated to run into this problem.