Yeah, I'd love a reproducible test case for this, if such exists 2011/11/10 Peter Neubauer <[email protected]>
> Wow, > never seen this before, do you have a full testcase to reproduce this? > > Cheers, > > /peter neubauer > > GTalk: neubauer.peter > Skype peter.neubauer > Phone +46 704 106975 > LinkedIn http://www.linkedin.com/in/neubauer > Twitter http://twitter.com/peterneubauer > > http://www.neo4j.org - NOSQL for the Enterprise. > http://startupbootcamp.org/ - Ă–resund - Innovation happens HERE. > > > > On Thu, Nov 10, 2011 at 9:18 AM, itoskov <[email protected]> wrote: > > I have this snippet of code while using neo4j embedded 1.4.2: > > > > Node newlyCreatedNode = db.createNode(); > > log.debug("NEWLY GENERATED NODE : " + > newlyCreatedNode.getId()); > > > > Node newlyCreatedNode1 = db.createNode(); > > log.debug("NEWLY GENERATED NODE 1: " + > newlyCreatedNode1.getId()); > > > > In most cases, this returns two different ids, but my problem is that I'm > > getting two same id values in two consecutive calls. > > For example: > > 2011-11-09 19:15:07,236 DEBUG - <NEWLY GENERATED NODE : 122766> > > 2011-11-09 19:15:07,236 DEBUG - <NEWLY GENERATED NODE 1: 122766> > > > > Can you tell me reason for this, or how to prevent this from happening > > > > > > > > -- > > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/id-problem-on-createNode-tp3496067p3496067.html > > Sent from the Neo4j Community Discussions mailing list archive at > Nabble.com. > > _______________________________________________ > > Neo4j mailing list > > [email protected] > > https://lists.neo4j.org/mailman/listinfo/user > > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [[email protected]] Hacker, Neo Technology www.neotechnology.com _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user

