Tried to use the extension, but it results that it is not performing
correctly in 2.0.
The method of creating the uuid in code and later assigning to the server
is the one i have been using. Even though the probability is very reduced,
I have no way from code to recursively try for a new uuid if it is already
existent in the db, specially because many of the objects are created
offline and only after user connects is that it can check with constraints
if the identifiers conflict.
On Monday, January 13, 2014 7:40:54 PM UTC-5, Michael Hunger wrote:
>
> There is for instance an uuid generating neo4j-extension from Stefan
> Armbruster which might be worth checking out.
>
> Otherwise you can also generate the uuid externally and use MERGE (n:User
> { uuid : {uuid}}) ON CREATE SET n.name = {name} return n
>
> Why do you want to assign an UUID to a relationship?
>
> Michael
>
> Am 14.01.2014 um 01:20 schrieb Jake Ortiz <[email protected]<javascript:>
> >:
>
> Currently I'm developing a social app for the iPhone with my computer as a
> server, and have bumped into a couple of obstacles. One I'm particularly
> trying to figure out is how assign an UUID to a node or relationship upon
> creation and if it already exists try again with a different uuid. I want
> to know if i there is anyway to implement this as a function like
> timestamp(). I'm developing on Neo4j 2.0.
>
> --
> 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] <javascript:>.
> 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.
