And I think optimizing for many years at once might be overkill Sent from mobile device
Am 01.02.2014 um 11:48 schrieb Brennan Kinney <[email protected]>: > I've spent some time building a query with the intention of saving time, > can't figure out what I've done that messed it up. The query is to build > years/months/days nodes/relationships and uses MERGE/CREATE UNIQUE to avoid > duplicates. Seems to work fine if I only use a single year, when I tried 6 > years at once Neo4j Browser returned "Unknown error". It had created plenty > of nodes/relationships however, using the query again even on a single year > (existing or not) would now also produce the "Unknown error". I've tried the > query in several db's including a new one, localhost and grapheneDB. > > One grapheneDB where I tested the query as I wrote it in steps gave this > error: > "The pattern (thisMonth)-[1469:`FIRST`]->(firstDay) produced multiple > possible paths, and that is not allowed" > That pattern is used with CREATE UNIQUE within a FOREACH. > > More information at StackOverflow, would love to know what I've done wrong, > or if it's a bug I'll post an issue on github. > http://stackoverflow.com/questions/21496051/neo4j-nested-foreach-query-failing > -- > 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.
