Quote:
Originally Posted by Farling
When I first started writing the Import tool I tried examining the UUID pattern that RW was using, and I couldn't marry up the UUIDs in the RW export files to any particular RFC-based UUID pattern.
My hope was that I could use the UUID pattern that included the date/time of creation of the UUID in order to create what would be a guaranteed UUID for the generated import tool. But without a guarantee that RW uses standard UUID patterns I wasn't able to guarantee that any self-generated UUIDs wouldn't conflict in the future with a UUID created internally by RW.
|
True, but I think there are a few thoughts on that. If the number were incremental, that means there is a way to convert it to a long number and just do one that is lower (milliseconds - 000, minutes - 60, hours - 60, days - 30, years - 12, decades - 3 (or at least back to 1-1-1970 if it was Microsoft). After all, the content markets and sharing a .rwstructure file between computers and even between realms on the same computer, the UUIDs might have collisions there, too.
This is all pure speculation for me, but at the very least, you should be able to do a partial by checking doing an export of the one you're importing to. Just run an XPath of //@global_uuid on your rwstructure file to list them out, find the smallest UUID's number, and make your imports significantly lower. Though there might also be stuff like a change in one of the of sets that states whether it is a tag, partition, facet, or whatnot.