Does anyone have advice (or know of a pattern) on implementing classes to represent lookup tables? We have a large number of simple id/name tables that I would like to cache at application start time. Typically I would just use the new enum featur in 1.5 but the values could potentially change and we'd like to be able to update them w/o having to recompile.
Login or Sign Up
- Log in with