Do Custom Vertex IDs Guarantee Single Instance of That Vertex?
Previously I was using a composite index with a unique constraint with locking to try to enforce uniqueness for new vertices, but switching to using that property as a custom vertex ID has a noticeable performance boost.
Just wondering if we're still guaranteed vertex uniqueness that locking previously would (try to) enforce?
I figured it does, assuming that custom vertex id is what's getting serialized to the backend. If so I'm guessing there literally wouldn't be a place for a doppelgänger to exist, but figured I'd ask since it wasn't explicitly stated in the docs after switching to custom vertex ids.
Just wondering if we're still guaranteed vertex uniqueness that locking previously would (try to) enforce?
I figured it does, assuming that custom vertex id is what's getting serialized to the backend. If so I'm guessing there literally wouldn't be a place for a doppelgänger to exist, but figured I'd ask since it wasn't explicitly stated in the docs after switching to custom vertex ids.
Solution
Just wondering if we're still guaranteed vertex uniqueness that locking previously would (try to) enforce?
Yes. And the reason is exactly what you suggested: the vertex id is what gets serialized to the backend. Good suggestion that we should have included it in the doc. Would you mind creating an issue or PR for that?
