One other reason.  It’s actually more consistent.   Consider when you’re creating a record:

 

reactorFactor.createRecord(“foo”)

 

Not

 

reactorFactor.createRecord(“foorecord”)

 

Doug

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jared Rypka-Hauer
Sent: Friday, April 14, 2006 11:49 AM
To: [email protected]
Subject: Re: [Reactor For CF] Removing record from getXyzRecord() methods.

 

And once again Doug reminds us of three core principles used by good programmers:

 

1) There is never one right solution (but some are way better than others).

2) Every choice you make is a trade-off between two or more conflicting concepts.

3) NOBODY looks good in baseball cap, not even baseball players.

 

This message brought to you by the letter J.

 

------------------------------------------------

Jared C. Rypka-Hauer

Continuum Media Group LLC

http://www.web-relevant.com

Member, Team Macromedia - ColdFusion

 

"That which does not kill me makes me stranger." - Yonah Schmeidler










 

On Apr 14, 2006, at 10:28 AM, Doug Hughes wrote:



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

-- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/

Reply via email to