Murat Demirci wrote:
The wrong with oQuery is related to its main intent. CF provides several
data passing techniques currently:
- simple values
- arrays
- structures
- queries
- xml
- custom components (like Person, AddressTO)
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.
The main intent of QueryIterator isn't data transfer. It just provides
another interface to iterate over a query and also provides stateful
iteration (remembers the position). Of course it can be used to transfer
data, but this is not the main intent.
However the main intent of oQuery is to provide a new object that holds
data, so it will force us to use it to transfer data. To implement this, you
are duplicating a query in the init method. This means it is an alternative
of "query" object. I don't believe developers need this oQuery component
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.)
since current data passing techniques are useful enough. 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.
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.
To help developers, there are some other windows to open like O/R mapper
tool, a more developer-friendly framework and maybe some code wizards like
new Login Wizard of Dreamweaver.
That doesn't work real well in Homesite, CFStudio (for those of us who
have a copy) or CFEclipse.
For example, I've developed a developer-friendly framework (MX Framework)
which will help developers to develop n-tiered OO applications more easily.
We can talk about it if you want.
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.
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]
