On Thu, Oct 28, 2010 at 11:12 AM, Michael Moore <michaeljmoore@xxxxxxxxx>wrote: > An alternative approach is to have many little "code tables". This approach > can have an advantage as the functionality of the system grows over time and > certain type of codes take on attributes of their own. > ... > The first approach of one or two tables to cover all codes promulgated by a popular book in the 09's as a performance enhancement. Personally I did not care for that approach. My preference is the many little tables as you have described, and now you have provided another reason for that preference. :) Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com