I've never tried separating my "one big query" into little queries. I'm not doing traditional query caching...
our mainframe application stores all of it's code descriptions in a single table... ie, pretty much every dropdown list in the entire database... from degrees to alumni activities to high schools (the high school part of the table is VERY large!) There are many places in the web site where I need to publish a code description, so I I query the code table and store the entire thing in the application scope (it only changes once a day) then I have a udf that generates the code desc on the fly using a query of queries... I actually exclude the high schools from the query and handle that "on the fly" from the db since there are very few places I use it, and it's a huge part of the table... essentially stores the high school name, city, state, and zip for every alumni in the system that we have that information for =) I've contemplated loading the data into individual structures instead... so I can access the individual descriptions by doing something like #controlcode['ALM21']# ... I susupect that might be faster than going to a UDF to do a query of queries on the code table. Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:270076 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
