The rule of thumb we (myself, Brian Kotek, Marc Esher, and Scott Stroz) are using on our first large CF ORM project is:
1. If a service is working with changing data, use ORM. 2. If an operation largely works with one item (e.g. a form or detail page), use ORM. 3. If we're going to show a list of things, especially across tables, get off our butts and write a decent SELECT statement to return a query. The common argument against using a select/vanilla query is "What it the getters in my objects model formatting/custom logic?" Our response to that is to factor that logic into a helper class that is a) used by the object and b) used where the query is cfoutput'd. -Joe On Fri, Oct 22, 2010 at 8:44 AM, enigment <enigm...@gmail.com> wrote: > > Just starting to look at the CF ORM stuff, pretty nice API, Hibernate > underneath, all good. > > But as I understand it, ORM "queries" return arrays of cfc objects, > and I'm concerned about performance at scale. On a gut level, I'd > rather be able to get a native CF query, which I could deal with in > straight CF as usual, or through an IBO if I wanted object-like > behavior for that whole collection. > > So... > > - Is it possible to have CF ORM return a query, when I want it to? > > - What's people's experience with this stuff at scale, meaning large > result sets, more than departmental traffic etc? Are there any largish > sites doing that? > > Thanks, > Dave > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:338480 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
