Thanks a lot for your engagement! What language / environment are you developing the driver for?
This is most efficient: - Multiple queries directly to /transaction/commit (creating a new transaction each one?) It depends on the usage though, if decisions for the following queries are made based on the results of previous ones then you'll probably want to support multiple requests within a single tx. Cheers Michael On Sat, Jan 25, 2014 at 11:42 AM, Gorka Lertxundi <[email protected]>wrote: > I started developing a neo4j client and when I reach to the transactional > endpoint there's something i'm not sure about: > > Which is the best option regarding to multiple 'MATCH' statements? (no > updates, no creates): > - Multiple queries directly to /transaction/commit (creating a new > transaction each one?) > - Create a transaction and then do MATCHes in it /transaction/5 (do > commit :\ after all?) > > rgds, > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
