hey dave, the long and short of it is: yes, it does impact performance, but for most people it is negligible. it has it's pros and cons just like anything, but if you ever are going to scale your app across multiple servers/clusters/cloud, then uuid is the way to go, due to it's "unique" nature.
take a look here: http://krow.livejournal.com/497839.html On Apr 17, 11:21 am, "Dave Maharaj :: WidePixels.com" <d...@widepixels.com> wrote: > I have been reading about Cakes' "Using UUIDs as Primary Keys" and in my > case I think it would be a much to get info from queries. But 2 questions. > > Would the tables now look similar to this? > User Table: id char(36) > Accociated Tables: user_id char(36)... (I know I had to ask...im new at this > and still on my first cake site) > > And what performace impact does this have on the database? Site I am > developing may have up to 20 thousand plus users.Its it going to be faster > because everything is tied to 1 unique id across all tables? Or will it slow > it down because of the size of the UUID? > > Thanks for any info, > > Dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
