Hi there, In my envisaged setup, I would have a centrally hosted "master" database, with users who may either use the master database, or use a local copy of the master database on their local machine. For these local copies, it should be allowed to create new vertices, that should eventually find their way back to the master database upon synchronization with the master database.
What is the best way to deal with the possibility that two local users would happen to create local vertices/edges with the same ID (which would lead to conflicts upon synchronization)? I was thinking about creating new local vertices/edges in a dedicated cluster, but this way I may hit the 32K cluster limit if the number of local users becomes quite large. Anyone have an idea? Maarten -- --- You received this message because you are subscribed to the Google Groups "OrientDB" 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/d/optout.
