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.

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

Setting search_path in startup packet #216

Merged
merged 1 commit into from Dec 1, 2014
Merged

Conversation

@alexismeneses
Copy link
Contributor

@alexismeneses alexismeneses commented Nov 20, 2014

As pointed out by @sehrope on PR #156, setting the search_path can be done directly in the startup packet when using v3 protocol, saving a round-trip.
Dealing with currentSchema is now done this way.

On v2 protocol, it keeps being set in an sql query after the connection has been made.

Note : I would consider merging PR #207 at the same time because I expect special characters to be now taken in account that way. And I think the behavior of currentSchema and setSchema() should remain consistent.

…p packet (v3 protocol only)
ringerc added a commit that referenced this pull request Dec 1, 2014
Setting search_path in startup packet
@ringerc ringerc merged commit c77cd4d into pgjdbc:master Dec 1, 2014
1 check passed
1 check passed
@davecramer
continuous-integration/travis-ci The Travis CI build passed
Details
@ringerc
Copy link
Member

@ringerc ringerc commented Dec 1, 2014

This is a sensible change. We should be doing the same thing for extra_float_digits if we've been told to assume a new enough server version, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants