BIRT 3.7
Written by: Michael Williams
Featured Refcardz: Top Refcardz:
  1. Scrum
  2. Apache Maven 2
  3. Essential MySQL
  4. Node.js
  5. Groovy
  1. jQuery Selectors
  2. Ajax
  3. Java
  4. Spring Config.
  5. Java Concurrency

Link Details

Link 51473 thumbnail
User 111696 avatar

By bloid
via weblogs.asp.net
Published: Nov 05 2007 / 16:06

There is only one commandment in the Gospel of the GUID: I. Thou shalt always use a GUID to uniquely identify a row in a table. Whenever I hire a new member for my team, this is one of the first rules that I teach them. At first, they almost always look at me like a puppy with their ears up and their head tilted to the side as if to say "huh?"
  • 14
  • 5
  • 1841
  • 0

Comments

Add your comment
User 60609 avatar

sigzero replied ago:

0 votes Vote down Vote up Reply

Thou shalt use the best thing for the task at hand!

User 238564 avatar

FlySwat replied ago:

0 votes Vote down Vote up Reply

This just goes back to the age old argument of natural vrs surrogate keys.

Personally, I prefer to use a GUID over a AutoIncrementing Int for my primary keys, however I'm not so short cited to write an entire blog post on why.

User 236137 avatar

dzonelurker replied ago:

0 votes Vote down Vote up Reply

His arguments are not bad but also not absolutely convincing.

User 60609 avatar

sigzero replied ago:

0 votes Vote down Vote up Reply

I am sure there are instances where you would want to use a GUID. I take issue with his "mandate".

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.