Additional comments, some are repeats... You should also consider the previous sentences:
>If current solutions are useful, what may force me to use oQuery? Some methods like sort, filter? I can do them with QoQ. I can also develop a UDF library for them which is stateless so cannot be used to transfer data. I still don't see a real-world reason to use oQuery. Here, the "current solutions" means "current data transfer solutions". Now, the main difference between QueryIterator and oQuery is more obvious: oQuery has its own data instance, it doesn't use external query. But again I'm mentioning there is no real-world reason to develop and use a new general data transfer object (oQuery). You know that Arrays are passed by value not reference which borns real-world issues. So developing an alternative collection for Array is meaningful. However we don't have similar issues with Queries in this case what is the real-world reason to develop an alternative for it? Also it will have its own problems like performance (this will be a really big problem for large queries). Trying to list some reasons to develop oQuery: - stateful iteration: queryIterator partially solves this. You can develop your own solution of course.. - development of sort and filter operations are hard: no I don't think so, if this is a reason a UDF library can solve this. - developers need some examples to start OOP: yes this may be true. But we can develop more useful OO solutions instead of oquery. - developers who migrate from ASP to CF needs ASP-style recordsets: is it really true :) no i don't think so. No, sorry, I cannot find a reason... Want to develop something? Let's talk about ordered collections, O/R mappers, CFC-UML converters, frameworks and tiers... Murat. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Adam Cameron > Sent: Monday, March 07, 2005 1:46 PM > To: [email protected] > Subject: RE: [CFCDev] query object CFC Beta > > >If current solutions are useful, what may force me to use oQuery? Some > methods like sort, filter? I can do them with QoQ. I can also develop a UDF > library for them which is stateless so cannot be used to transfer data. I > still don't see a real-world reason to use oQuery. > > How come you don't apply this sort litmus test to the queryIterator? The > same thing applies: it's not doing anything new you can't already do. But > it's a pointless benchmark anyhow, as it kind of misses the point that the > object of the exercise is to encapsulate the functionality in one place, so > that it happens to already exist in other places is beside the point. > > -- > Adam > > > This email contains confidential information. If you are not the intended recipient of > this email, please notify Straker Interactive and delete the email. You are not > entitled to use it in any way. > > > ---------------------------------------------------------- > You are subscribed to cfcdev. To unsubscribe, send an email to > [email protected] with the words 'unsubscribe cfcdev' as the subject of the > email. > > CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting > (www.cfxhosting.com). > > An archive of the CFCDev list is available at > www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
