Update to pg_query 0.9.1, adds PostgreSQL 9.5 syntax support #6
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
|
@purcell I see the tests are unhappy about the missing 1.9 support (pganalyze/pg_query#44) - I actually have a fix for this in the pipeline, I'll try to release a new version that supports 1.9 today and update the PR. |
|
Awesome, thanks. |
|
(And thanks for pg_query!) |
lfittl
changed the title
|
@purcell 0.9.1 released - tests are green now 🎉 |
|
Yay, thanks so much for this. |
|
New gem version 0.1.4 pushed. :-) |
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.
First of all, thanks for building this on top of pg_query! :)
I saw you are using an older version of pg_query right now (0.5), and I recently released 0.9.0 - which amongst other improvements is based on PostgreSQL 9.5 - which means
sqlintwill also support UPSERT once you upgrade.Tests all pass, I had to fix a minor detail with error messages (they are more verbose now), but output should be identical for the end user.