JDBC Prefix different to 2.x about neo4j-jdbc HOT 5 CLOSED

For me it's just redundant with the driver class, but I see your point.

If we add the neo4j prefix, we must adding it to all url.
So do you prefer solution 1 or 2 ?

• jdbc:bolt://localhost & jdbc:http://localhost (1)
• jdbc:neo4j:bolt://localhost & jdbc:neo4j:http://localhost (2)

from neo4j-jdbc.

I think there are some tools that infer the driver class from the URI. Currently I would prefer solution 2.

from neo4j-jdbc.

I agree, this seems to be important in mixed environments.

from neo4j-jdbc.

I would also prefer solution 2!

from neo4j-jdbc.

In my opinion solution 2 is much more clean and clear.

from neo4j-jdbc.