It's usefull if you have more than one database server (cluster). Instead of working with auto-increment columns to identify your rows you use uuid's instead. You'll then have no problems if you want to merge the tables from all those or some of the nodes (hardware upgrades, so that e.g. three nodes get merged into a new one), because they all have unique ids.
On Mar 22, 7:18 pm, "Hadrien Boyé" <[EMAIL PROTECTED]> wrote: > hi, > > i can't figure out in which scenario it would be useful to generate such a > complex identifier. can you give me an example ? > > thanks. > > hadrien > > 2007/3/21, Tristan Rivoallan <[EMAIL PROTECTED]>: > > > > > hi, > > > On 3/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > works for me now - thanks. > > > > I researched a little bit regarding the Uuid in Mysql. I read that the > > > main problem is the big index size they are creating when use very > > > much. > > > This is a fact. Plus guid indexes are not as efficient as autoincrement > > indexes due to the unpredictability of the guid. > > > Due to some colleques work it would be much faster to use a > > > number or binary representation for the guids in the db. do you have > > > any thought about this? > > > i'm not sure i understand. By "number" you mean using autoincrement ids ? > > What would the binary representation of a guid look like ? > > > afaic, i use guids to guarantee resources uniqueness for replication means > > (application level replication). > > > sorry about the probable misunderstanding ;) > > > ++ > > tristan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
