What To Do About Chatty Data Models?
796254Feb 14 2005 — edited Feb 15 2005I'm working on a legacy app that has some DAOs that are "chatty". There are multiple methods, each with different SQL, that bring back primitive values (e.g., double, String, etc.) This DAO is written in such a way that assembling one DTO to return to the client takes 70 distinct calls, each with its own network roundtrip.
What's the best way to go about correcting this?
Combining those disparate SQL queries into one big JOIN is a daunting task, made complicated by some other features in the implementation.
Is a stored procedure a possible solution? We're using Oracle 8i as the data store.
%