See the comments below

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of
> John Farrar
> Sent: Tuesday, March 08, 2005 2:16 AM
> To: [email protected]
> Subject: Re: [CFCDev] query object CFC Beta
> 
> Sorry I didn't make my point clear. oQuery has diverted from the
> iterator purpose. I am on a different path and not intending to fill the
> purpose with my object that it started on. (Note: for iterating you
> might try a CF_customTag and use <cfexit mode="loop"> in the end tag
> code segment. Read the docs... this might be more useful to you than an
> object.) Custom tags were never explored by the CF community at large
> like the CFC's have been. It's a shame! They are quite useful even
> today. I think Forta had it right when he stated the difference in uses.
> Look it up on his blog.

Yes, I've used <cfexit mode="loop"> and hidden (moveNext(), etc) methods.
They provides iteration (increases myQuery.currentRow). But it fails when we
want to use dotted notation (myQuery.myField). I'm looking for offical
support... will go to the wish list. Thank you for your help.

> Then don't use it. (It's an "extended" alternative, yes. And yes
> normally I would not use this object either... but there are some times
> it is a good low traffic solution... or a stop gap until a full tested
> update can be put into place with regression testing and such. I am sure
> that you will do fine without it. It's OK with me if you don't see the
> benefit it gives my development team.)

I don't use it. (I couldn't pull myself from this discussion due to my poor
English. Seriously.)

> Again... contrary to your above "it will force us to use it..." and
> "what my force me to use oQuery?"... that is not my intent. Use the
> query iterator for your needs that will work for you and honestly you
> can relax... nobody that I know of is trying to force you to use my
object.

Sorry it is a mistake. I meant "it will force us to use it as data transfer
object in all layers when we use it once. If you design oquery as a helper
manipulator object like QueryIterator, in this case, what will the reason to
use it? Sort and filter? We have some weak arguments for QueryIterator, but
do we have some arguments for oQuery if you design it as helper object like
QueryIterator?"

> nobody that I know of is trying to force you to use my object.
John I haven't want to mean this. Of course I always have the option not to
use it. Sorry to cause misunderstanding.

> I have done that also... it was a great experience. Hope yours is as
> useful for you as mine is for me. If you want to swap ideas that sounds
> like a useful time exchange. Send me a note oflist. Would be glad to
> chat on that one.

OK.

Murat.



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

Reply via email to