Tuesday, December 8, 2009

Just in case...


Just in case the gubmint decides to add another month.
Obamuary, anyone?

  So, I can't decide...  is the height of laziness or the height of malfeasance?  Sure, I guess it could really be a hassle to type out the names of the months again and again for drop down lists, but only if you don't know how to write it once in an include file or library.  The laziness here could be either being too lazy to type the months repeatedly or too lazy to learn how to not type the names repeatedly.  If, on the other hand, this user is aware of the cost of a database connection and chooses to pull this mundane list every time someone needs to fill in a date drop down, then I say Bravo!  That'll show 'em.  Show 'em what, I can't say, but, by gum, it will show them.

(submitted by anonymous)
at 6:33 AM
Labels: ,

3 comments:

Hero Interactive said...

Meh, I don't think there is enough information to judge the stupidity of this one.

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.

b) It may be following company convention for the project and may simply be being consistent with past code.

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't be that much of a hit in performance.

Or it could be just stupid...

January 3, 2010 7:56 AM
Dharvabinky said...

True... I guess I didn'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. ;)

January 4, 2010 6:48 AM
Aditya said...

I'm less than n00b with dbs, but suppose you've got a nicely normalized db and other tables refer to month by index...

January 16, 2010 10:37 AM

Post a Comment

Subscribe to: Post Comments (Atom)