Hi Scott, Unfortunately you cannot force RID generation, even from binary interfaces.
Creating and detaching a node is an option, but I don't think it's the most effective one. IMHO a simple db backup/restore will do the trick in a much more efficient way Thanks Luigi 2016-07-25 10:01 GMT+02:00 'scott molinari' via OrientDB < [email protected]>: > Thanks Luigi, > > When you say, "provide a script", are you talking about a program written > in say Java or Node (or even PHP)? If yes, can the RIDs actually be > forcefully set through the binary interface? If so, how would ODB know > where to start with the next RID on the next record creation? > > The different RIDs is exactly what we want to avoid. There is a really big > cloud PaaS player, who has a sandboxing system, but they always change the > IDs of the records, which makes the programming a lot more difficult, > because the references are always lost. It means, anyone using the system > has to basically program without any references to IDs and this is just > plain difficult. > > Could it also be possible to have a distributed setup and to create a > sandbox, create a new node in the cluster (slave?), then disconnect it and > run it standalone? After that point, it is considered a sandbox copy? > > Scott > > -- > > --- > 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. > -- --- 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.
