Hi, Is there a size limit to the documentID? I know it's best to keep them small, but I may need to prefix them with a UUID to guarantee uniqueness.
Here's my situation. Due to legacy data the user may have acquired outside of my app, a user may have a record with ID "12345" in it. So when importing into my app, I use that as the documentID. There are a couple of ways I'm thinking about handling this. One is to add a secondary key to my document "legacyID" or something like that and generating a UUID for the documentID. That means though that I have to keep track of a dictionary of legacyID to UUID mappings because I have all sorts of relationships that I manage during the import process. That's not too bad though. The other thing I was thinking was just to prefix or append a UUID to the existing key. But sometimes the existing keys are pretty big themselves. So that's why I was wondering if there was a limit to the key size. Thanks, Brendan -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/a7767b79-1fe5-46d3-8de5-6d6cc953c075%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
