Frankly, the deprecation might be overkill.
When constructing a driver via GraphDatabase.driver(...), you cannot run into this case, but only when using the undocumented and cumbersome GraphDatabase.neo4j_driver(...) method. Even then, the driver will ignore everything but the first target.
Frankly, the deprecation might be overkill. When constructing a driver via
GraphDatabase.driver(...)
, you cannot run into this case, but only when using the undocumented and cumbersomeGraphDatabase.neo4j_driver(...)
method. Even then, the driver will ignore everything but the first target.