title: Enum and performance
body: <p>My app has a lot of different lookup values, these values don't ever change, e.g. US States.  Rather than putting them into database tables, I'd like to use enums.</p>
  
  <p>But, I do realize doing it this way involves having a few enums and a lot of casting from "int" and "string" to and from my enums.</p>
  
  <p>Alternative, I see someone mentioned using a Dictionary&lt;> as a lookup tables, but enum implementation seems to be cleaner.</p>
  
  <p>So, I'd like to ask if keeping and passing around a lot of enums and casting them be a problem to performance or should I use the lookup tables approach, which performs better?</p>
  
  <p>Edit: The casting is needed as ID to be stored in other database tables.</p>