Update sequel: 5.23.0 → 5.24.0 (minor) #18
Closed
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ sequel (5.23.0 → 5.24.0) · Repo · Changelog
Release Notes
5.24.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
Bump version to 5.24.0
Update CHANGELOG
Add spec to cover skip_logging? override method
Extract logging guard to own method
Use actual operator class in documentation
Document how to use operator classes in exclusion constraints (Fixes #1639)
Update CHANGELOG
Remove unnecessary localhost assumption
Convert all database array types to Ruby arrays in the jdbc adapter
Add a couple specs for better coverage
Add static_cache_cache plugin for caching rows for static_cache models to a file to avoid database queries during model initialization
Add :cache_file plugin option to pg_auto_constraint_validations plugin, for caching metadata to a file for faster initialization
Support :unique_deferrable and :primary_key_deferrable column options
Support :generated_always_as column option on PostgreSQL 12+
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands