Skip to content

routing: Fix default database name in the routing connection provider #653

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

Merged
merged 1 commit into from
Dec 17, 2020

Conversation

bigmontz
Copy link
Contributor

A RoutingTableRegistry was extracted from the Connection Provider to help re-use
some behaviours.

@bigmontz bigmontz requested a review from 2hdddg December 15, 2020 13:42
A RoutingTableRegistry was extracted from the Connection Provider to help re-use
some behaviours.
@bigmontz bigmontz force-pushed the 4.3-fix-routing-table-registry branch from 79aa880 to 08d19eb Compare December 17, 2020 11:36
@bigmontz bigmontz merged commit 9b3211a into neo4j:4.3 Dec 17, 2020
@bigmontz bigmontz deleted the 4.3-fix-routing-table-registry branch December 17, 2020 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants