>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]
