Skip to content

Added database name in the ResultSummary. #591

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 4 commits into from
May 7, 2019

Conversation

zhenlineo
Copy link
Contributor

This requires the server to stream db with database name in the result summary.

@zhenlineo zhenlineo marked this pull request as ready for review April 29, 2019 10:03
@zhenlineo zhenlineo requested a review from ali-ince April 29, 2019 10:03
@zhenlineo zhenlineo force-pushed the 2.0-database-name-in-summary branch from 5818f3d to bae2507 Compare April 29, 2019 12:09
Copy link
Contributor

@ali-ince ali-ince left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good. I only think that we should throw ProtocolException on unexpected types in summary.

Zhen Li added 2 commits May 6, 2019 13:37
The database name default to `null` if the server does not support multi-databases when the database name is returned in result summary.
However `null` is a forbidden value for database in session parameters. Then for user who want to connect to default db but do not want ot omit invoke `withDatabase` method on session parameter, they have to use empty string to work aroud our API design.

This PR allows `null` as a valid database name for session parameters, while disallows empty string as it is an invalid database name to users.
@zhenlineo zhenlineo force-pushed the 2.0-database-name-in-summary branch from 35ebb4e to 80203b3 Compare May 6, 2019 13:31
@zhenlineo zhenlineo merged commit d5a4554 into neo4j:2.0 May 7, 2019
@zhenlineo zhenlineo deleted the 2.0-database-name-in-summary branch May 7, 2019 13:03
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