Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixed #5747, Properly parse Int4 range types #6220

Merged
merged 1 commit into from
Jul 5, 2016
Merged

Fixed #5747, Properly parse Int4 range types #6220

merged 1 commit into from
Jul 5, 2016

Conversation

sushantdhiman
Copy link
Contributor

Pull Request check-list

  • Does npm run test or npm run test-DIALECT pass with this change (including linting)?
  • Does your issue contain a link to existing issue (Closes #[issue]) or a description of the issue you are solving?
  • Have you added new tests to prevent regressions?
  • Have you added an entry under Future in the changelog?

Description of change

Fixes #5747 , Incorrect OID was used for Int4 in range type.

@sushantdhiman sushantdhiman changed the title Fixed #5747 Fixed #5747, Properly parse Int4 range types Jul 4, 2016
@sushantdhiman
corrected oid for range Int4
558129d 
Conflicts:
	changelog.md
@sushantdhiman
Copy link
Contributor Author

Rebased

@sushantdhiman
Copy link
Contributor Author

All Green @mickhansen @janmeier , Let me know your comments. Once its merged I will rebase next one.

@janmeier janmeier merged commit b580d80 into master Jul 5, 2016
@janmeier janmeier deleted the fix-5747 branch July 5, 2016 07:49
@FREEZX FREEZX mentioned this pull request Nov 19, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@janmeier janmeier

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@sushantdhiman @janmeier