pf » Use Char instead of Varchar to Store UUID's

Use Char instead of Varchar to Store UUID's

databases

I know a lot of developers like using UUID's for primary keys instead of integers. But one thing I see alot is the use of the varchar datatype to store these strings.

If your using ColdFusion's CreateUUID() function to generate a unique identifier, you will notice that it always returns a 35 character string. So why store it in a variable length column in the database? Instead of using varchar (35) you can simply use char (35).

As a rule, if you are storing a fixed length string in a database use char rather than varchar. A varchar will have an extra byte of overhead on most databases (usually an integer stating the actual length of the string).

Some other common places where you should use char over a varchar include:

  • Two Character US State Codes
  • Two Character Country Codes
  • One Character Status Flags


Related Entries
8 people found this page useful, what do you think?

Trackback Address: 626/AC7AB70DC80071CFC039692BD3380691
On 01/18/2008 at 1:22:09 PM MST Daniel wrote:
1
UUIDs are always 36 characters long, and not 35. Look up the standard.




  



Spell Checker by Foundeo





Subscribe to my RSS Feed: solosub RSS
Tags