OK, but please all take into account that it is not necessarily the best thing to tie the creation of the UUID to the database at all. That would be a big mistake and bad design decision and continue the kind of dependencies that need to be overcome. There exist many independent UUID libraries (in Java, PHP, etc) as described in the other thread. Once created, the UUID of course will be persisted, so the rest of the discussion is exceedingly fruitful, especially the use cases. Victor Kane http://awebfactory.com.ar On Sun, Aug 10, 2008 at 7:52 PM, Robert Douglass <rob@robshouse.net> wrote:
Again, a driving use case is "two drupal sites that were founded independently of any knowledge of each other would like to merge their databases".
To me, two even more compelling use cases are:
a) sharing global taxonomy vocabularies (the countries of the world each have globally unique ids shared across all sites) b) import/export. This is like the merge example from Ethan but perhaps a little more concrete in terms of what people are already doing. I could export my blog posts from one site and import them into another site and keep the id. c) global user ids. I always have the same user id on every Drupal site.