If it's not related to other information in the database and don't change, I'd put them into a file (CFM, TXT, XML, whatver) and then cache them in the APPLICATION scope. If it's not even application dependant (like states), then put it in the SERVER scope. If it's application dependant data (product categories), the read that from the DB and cache it in the APPLICATION scope.
If it never (or rarely) changes, cache it in memory, since dropdowns are generally very small, especially if you'll be using it frequently. > -----Original Message----- > From: James Blaha [mailto:[EMAIL PROTECTED] > Sent: Friday, March 21, 2003 11:40 AM > To: CF-Talk > Subject: Just wondering Lookup Tables > > > Hello All: > > Just wondering what you all do out there for application lookup tables > for dropdown selection options. Do you use one table for all your > dropdowns and classify them or do you make a separate table for each > dropdown? I’m not sure what the best route to go is. > > For example a state lookup, or a list of options like select one > of 20 cars. > > Regards, > James Blaha > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
