Yes, that's the idea, you should be able to use the same connection. For transactional operations though to use multiple transactions in parallel you'll have to use multiple threads, as the tx handling is thread bound.
I personally think the JDBC driver is currently a sensible way to access Neo4j from Java, except if you want to POST to the transactional http endpoint yourself using any http or restful client library. Michael Am 25.08.2014 um 13:38 schrieb vaibhav nirkhe <[email protected]>: > Team, > This is regarding Neo4j-JDBC driver ,from the code of this > library it looks like we can have a single connection cached to cater all the > statements/requests in the application we just need to create new statements > everytime . Please suggest if I am understanding this correctly ? Or else we > need to maintain a pool of objects ? > > Also let me know is using Neo4j JDBC driver is the standard way to connect > through Java or we have better ways to do that(like Java API or REST > interface) . > > > Thanks in advance !! > > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
