Felix Geisendörfer [EMAIL PROTECTED] wrote:
I'm looking for someone to give me a hug and tell me everything will
be ok.
I'll go ahead and do this: *hug*
*hug* everything will be okay.
--
Chris Lamb, Leamington Spa, UKGPG: 0x634F9A20
signature.asc
Hi there,
I'm looking for someone to give me a hug and tell me everything will be ok.
Thinking in terms of low coupling of classes again, it struck me that
passing your applications method parameters as associative arrays may be a
step in the wrong direction. For example, I have a cake component
I'm looking for someone to give me a hug and tell me everything will
be ok.
I'll go ahead and do this: *hug*
Regarding your topic: I think you are getting a little paranoid here.
Yes high coupling is something you want to avoid. Coupling itself
however is not your enemy, it's how you write
Hi Nate,
I knew you'd answer this one :)
On 3/21/07, nate [EMAIL PROTECTED] wrote:
First of all, the coupling would not be any looser even if you used
objects. The component would just be tightly coupled to an object
property instead of an array key. Second of all, this is what
afterFind
Yo Felix,
On 3/21/07, Felix Geisendörfer [EMAIL PROTECTED] wrote:
I'm looking for someone to give me a hug and tell me everything will be
ok.
I'll go ahead and do this: *hug*
Thanks dude :)
When however you are writing a database depended application you have to
accept that field names
First of all, the coupling would not be any looser even if you used
objects. The component would just be tightly coupled to an object
property instead of an array key. Second of all, this is what
afterFind is for. If you have to make a database change which impacts
your code, you can use
