Wednesday, February 29, 2012

Re: Using char(36) as a uuid

There is some debate that keys should be meaningful, and I get that - but a UUID is as meaningless as an auto incremented key.

With judicious use of routes, configuration, and other such bits you can utterly hide your IDs from public scrunity if that is what you're worried about... personally I find it much easier to navigate to posts/5 as opposed to posts/aeasd12382nd2jujud3nx3juo3ehu9282 but maybe thats just me.


On Thu, Mar 1, 2012 at 7:26 AM, Miles J <mileswjohnson@gmail.com> wrote:
Whats the reason for disliking auto-incrementing numbers? Its probably the best thing about databases.


On Wednesday, February 29, 2012 6:53:38 AM UTC-8, Ighor Martins wrote:
Hello,

I was thinking about the use of integer as primary key of the table or use a char(36) as UUID in the entire project,
What I dont like about the integer, is the auto increment number, So I decided to use char(36) 'cause cake automatically fill it with an UUID, but I dont know if this can slow down the search in DB.

So, anyone who used this before, please tell me about that.
Is that right to use this in tables like: Users, Cars, Categories?


Thanks.

--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
 
 
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php

--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
 
 
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php

No comments: