tag:blogger.com,1999:blog-8932343929537766493.post4054230682813796737..comments2010-01-16T10:37:46.371-08:00Dharvabinkynoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8932343929537766493.post-70783089578529129542010-01-16T10:37:46.371-08:002010-01-16T10:37:46.371-08:00I&#39;m less than n00b with dbs, but suppose you&#39;ve got a nicely normalized db and other tables refer to month by index...Adityahttp://www.blogger.com/profile/06265541752604506523noreply@blogger.comtag:blogger.com,1999:blog-8932343929537766493.post-21806046222362224412010-01-04T06:48:58.227-08:002010-01-04T06:48:58.227-08:00True... I guess I didn&#39;t think about localization when I got this post in the drop box. *grin* The other 2 cases, however, still seem to qualify it for ICHDJ. ;)Dharvabinkyhttp://www.blogger.com/profile/04499676211644652134noreply@blogger.comtag:blogger.com,1999:blog-8932343929537766493.post-26093457818354941362010-01-03T07:56:05.627-08:002010-01-03T07:56:05.627-08:00Meh, I don&#39;t think there is enough information to judge the stupidity of this one.<br /><br />a) It seems unlikely that months will change, but if this application is going to be localized into other languages having it in a database may be useful.<br /><br />b) It may be following company convention for the project and may simply be being consistent with past code.<br /><br />c) If the database is local on the machine and is just for a specific app on the same machine for that user (which is lame I know, but sometimes the case), there wouldn&#39;t be that much of a hit in performance.<br /><br />Or it could be just stupid...Hero Interactivehttp://www.herointeractive.comnoreply@blogger.com