|
Well, I find that I can be much more
specific about what I want when I just use a regular query. The advantage
comes down to getting just what I need in a very natural manner. The disadvantage
is that it’s not as portable. Don’t get me wrong. I still value the OO
queries and plan to enhance them over time. I just forgot the purpose behind
reactor for a bit: automate repetitive coding. These queries are not
repetitive. They’re very specific for a particular purpose. It makes since to
write them out. This is consistent with the purpose of reactor. Doug From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Kenney So, any reason in
particular that you are not using OO queries so much any more? Are they harder
to formulate or too limited for many things? On 4/14/06, Doug
Hughes <[EMAIL PROTECTED]>
wrote: The iterator is going to be tweaked a bit too. Right
now the iterator is cached in the record. That's not right. It
shouldn't be for various reasons. That and I'm going to try to make it
possible to add and delete items from Iterators and have saves and validates
intelegently cascade. The same thing for hasOne relationships as
appropriate. The current event model is just not natural and I've learned
a few lessons on how this could be made efficient. I'm also considering downplaying the importance of oo
queries. As I work with reactor more and more I'm avoiding them for much
of anything other than the most basic queries. (We'll see here)
They'll definitely continue to be there and probably unchanged forever for the
framework itself to use. Doug
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Jared Rypka-Hauer Wow...
cool. I've got
both in mine because I tweaked the XSL... but yeah, it is very natural. And
getObjIterator() still feels right, even with that change. Laterz, J ------------------------------------------------ Jared
C. Rypka-Hauer Continuum
Media Group LLC Member,
Team Macromedia - ColdFusion "That
which does not kill me makes me stranger." - Yonah Schmeidler On Apr
14, 2006, at 8:58 AM, Doug Hughes wrote: FYI
also, I've been playing around in my code with not referring to things as
records and have found it to be very natural. As a result I'm very likely
going to remove the "Record" portion of the getXyzRecord() methods
before beta. Thus getXyzRecord() will become getXyz(). Doug --
Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
-- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
|
- [Reactor For CF] Removing record from getXyzRecord() met... Doug Hughes
- Re: [Reactor For CF] Removing record from getXyzRec... Jared Rypka-Hauer
- RE: [Reactor For CF] Removing record from getXy... Doug Hughes
- Re: [Reactor For CF] Removing record from g... Paul Kenney
- RE: [Reactor For CF] Removing record fr... Doug Hughes
- Re: [Reactor For CF] Removing reco... Jared Rypka-Hauer
- RE: [Reactor For CF] Removing ... Doug Hughes

