On 9/25/06, Doug Hughes <[EMAIL PROTECTED]> wrote:
The time to convert OO queries to sql. The time spent executing the query isn't as big of a deal (although it would be nice to be able to cache some of that data at some point).
It seems to me that most of the OO queries are constructed afresh on each request, yes? Most all of the code I've seen (both inside the framework and outside) seems to construct a new OO query each time it is executed so all you are going to be able to do is somehow identify that a given object tree has already been seen and translated and short-circuit the transformation back from OO to text. For the internal OO query constructions, such as the read() method in the DAO, isn't that somewhere you could short-circuit the *construction* (of the OO query) as well, by using a different structure to hold the internal where clauses? -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
