UUIDs need way more "disk space". one might add that speed can also be
an issue.
having tables with a lot of foreign keys can be slowed down quite a
bit, even with indexing.
we have a project with uuids and tables with 1xxxx records get really
really slow.

on the other hand UUIDs are very handy if you want to "hide" the
current record count.
with AIIDs you always know how many users have been registered (= how
popular your site was):
200, 6000, ...
with UUIDs you have so such statistics anymore. this can be unwanted
or desired.


On 14 Jan., 19:31, jeremyharris <[email protected]> wrote:
> UUIDs are entirely unique while autoincrement ids are unique just for that
> table. The benefit of UUIDs would be for things like merging tables,
> merging other data, migrating the data elsewhere, etc. With UUIDs you
> guarantee there won't be conflicts.
>
> It's a matter of preference and depends on your project.

-- 
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
[email protected] For more options, visit this group at 
http://groups.google.com/group/cake-php

Reply via email to