I never claimed that my solution is very OO. However, I treat DB interaction CFCs as objects - the more general cfc is inherited by child CFC and all cfcs encapsulate some functionality (like variable caching). Granted that I only need a single instance of my object and not much manipulation is done to that object.

I am curious as to how other people deal with database interaction issues, does anyone take similar approach to mine?

TK

----- Original Message -----
  From: Dave Watts
  To: CF-Talk
  Sent: Thursday, October 30, 2003 8:56 PM
  Subject: RE: CF treatment of queries inside CFCs

  Well, it sounds like you couldn't leverage OO any less, actually. As Matt
  said, that's not necessarily bad, but putting functions in CFCs does not
  make something OO. If you were using objects in the OO sense of the word,
  those objects would represent individual entities that your program
  describes. For example, if you had a program that dealt with cars, when your
  program talked about a new car you'd create a Car object, which you'd treat
  more or less like any other variable.


[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to