Different opinions about these sort of approaches exist, some people keep telling others that this is the right approach because you won't mix different types of objects.. , my opinion out of personal experience .. don't do this.
I have code reviewed many applications, and this approach of getting values is the absolute number one cause of bad performing applications. Despite keepalive connections, each request to the database server requires startup en shutdown time. Each request requires a thread, each request requires an execution of the query, and this really cripples servers with ease. This is even worse, if your database server isn't on the same machine. I'd personally only use one query. Or at least, try to execute as less queries as possible. Then convert the dataset to for example a structure. I know some of the people are against this, but I have never found a situation where bad performance and sluggish code outweighed more efficient code. This has nothing to do with premature optimizations also, this has to do with initial approach for getting data with a lot of properties. Micha Schopman Software Engineer Modern Media, Databankweg 12 M, 3821 AL Amersfoort Tel 033-4535377, Fax 033-4535388 KvK Amersfoort 39081679, Rabo 39.48.05.380 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware: a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:190894 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
