Merge dev/0.6.5 branch into master ahead of release #369
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.
I wanted to move every non-breaking change into a patch release, so that people could upgrade easily without needing to go to 0.20.0. I think this is going to take some of the pressure of the 0.7.0 release.
As part of this cleanup, I also squashed the separate commits from PRs into one single commit, to make this history seem much cleaner.
Once merged and released, I'm going to rebased dev/0.7.0 onto this branch, and clean up the commits that I'm keeping on there. That should put us in great shape to focus on the 0.20.0 changes
Here's the summary of commits that were on the
dev/0.7.0
branch, and where I've now represented them :)unique_combination_of_columns
schema test in order to support aWHERE
argwhere
for free in 0.20.0