Hi, On 04/10/16 16:02, Julian Reschke wrote:
At least in our DocumentStoreImplementations (Mongo and RDB), making the UUID something indexed by the storage (so either Mongo or the relational database) should be relatively cheap (after all, the UUID never changes once assigned, right?).
The jcr:uuid of a node mapped into a document *can* change. Consider the case where a referenceable node with a given path is created, then removed and re-created again with a different UUID. Regards Marcel