I’m going to let the world weigh in on this.  I don’t see how it’s different from getXyzRecord()

 

Doug

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Phillips
Sent: Friday, April 21, 2006 8:54 PM
To: [email protected]
Subject: Re: [Reactor For CF] A few minor bug fixes committed.

 

Well, that wouldn't have happened with getFormRecord()......

Just razzing.

So really though.
Since we're in alpha,
What do you thing about getting rid of that problem by using the naming convention getRelated['object']() so in your example getRelatedForm() ?

Cause I can see lots of naming clashes with getX naming for hasOne relationships...

Thanks,

Chris Phillips

On 4/21/06, Doug Hughes <[EMAIL PROTECTED]> wrote:

 

Hey all,

 

I committed a few minor bug fixes.   One thing of particular note is that the getParent and setParent methods have been renamed to _getParent and _setParent to avoid conflicts with generated method names.  For example, if your table has a column named parent.

 

Also, as a tip, I had a table a column named which happened to have a hasOne relationship with a table called form (via a formId column).  That same table had a field named form.  When I generated the record for this object I got duplicate method names. The reason is that the hasOne relationship created a method called getForm.  So did the form field.  To get around this I had to either add a field alias or an alias on the hasMany relationship.

 

Doug 

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




--
Chris Phillips
www.dealerpeak.com
Senior Application Developer -- 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/

Reply via email to