Re: Does every model really need a "name" field? --psybear

You do not need to have either a name or title field in your table, but they have their uses. Cake can use a 'name' or 'title' field to automatically populate lists and such. Having said that, you can override it with var $displayField in your model. See: http://book.cakephp.org/view/1014/Titles for more info.

I prefer to stick to a name field as Cake drives convention.

Jeremy Burns
Class Outfit

jeremyburns@classoutfit.com
http://www.classoutfit.com

On 4 Nov 2010, at 08:18, Joshua Muheim wrote:

>> Is this what you mean??
>
> I guess not really... I have taken over an existing application where
> every table has a name field. So I wonder if this really is a "must"
> or not.
>
> I'm aware that every model needs a $name variable, thank you. :-)
>
> Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.
>
> You received this message because you are subscribed to the Google Groups "CakePHP" group.
> To post to this group, send email to cake-php@googlegroups.com
> To unsubscribe from this group, send email to
> cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en

Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.

You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en