Why I use UUIDs for primary/foreign keys

[eluser]slowgary[/eluser]
I use integers as well, but have looked at UUIDs. Mainly the reason that I hadn't switched was that I feel comfortable with using integers already, but I hadn't really looked at pros and cons so this thread helps.

I can add to the argument of uniqueness though. UUIDs are unlikely duplicated, but that doesn't mean it's not possible. If you handle the possibility of duplication then you're okay. BUT, you can't really argue that they're more unique or less likely to collide as integer IDs, because integer IDs are auto-incremented, so there will NEVER be a collision, and you don't need to write the code to handle one.

I do see where UUIDs would make combining tables easier, but I've never had need to combine tables and if I did I'd probably just have to write a script to handle the IDs.

I think for simplicity I will stick with integers but if I had a need for a bit of extra security/obscurity of data in an app I will consider UUIDs.