Correct, there are no guarantees on ordering. I thought this was documented in the core API but it seems to have been left out. Thanks for asking and pointing this out, we will add that piece of information before the 1.0 release.
-Johan On Thu, Dec 10, 2009 at 11:31 PM, Rick Bullotta <rick.bullo...@burningskysoftware.com> wrote: > AFAIK, no guarantees on ordering, thus the reason for the indexing > utilities. > > -----Original Message----- > From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On > Behalf Of Adam Rabung > Sent: Thursday, December 10, 2009 5:15 PM > To: Neo user discussions > Subject: [Neo] Ordering of getRelationships > > Hi, > I was wondering if there are any guarantees about the order of relationships > that come out of Node.getRelationships? In my test case (attached) it seems > they come out in "creation date, ascending" order, until you close and > re-open the database. After the database is reopened, it seems like the > order is reversed. For example: > 1. Create a parent > 2. Add child c1 > 3. Add child c2 > 4. getRelationships on parent returns c1, c2 5. commit and finish 6. > getRelationships on parent returns c1, c2 7. Shutdown and reopen 8. > getRelationships on parent returns c2, c1 > > It's been a long week, and I'm convinced I'm messing something up here. > > Thanks, > Adam _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
