Thanks for the input
> > I agree that it sometimes can seem like overkill. However, defining > > such things in bootstrap creates a separation that doesn't seem very > > elegant to me. I'd rather have the association completely within the > > DB. Using an ENUM column within the main table might be better, if > > Cake supported them (I believe it still doesn't), but it's not really > > too big a deal from the database's perspective to have a bunch of very > > small tables for this purpose. Not all tables need be updated often, > > and some databases allow for optimisation of just these sorts of > > tables, in any case. > > -- > Once upon a time I thought you had to create a controller for these types of tables.. oh dear. I suppose the advantage is that you can interact with the data using a model - even if it's just a simple afterFind to convert the datetime format on created and modified fields. I think I'll use that method, even if I have approximately 20 of these fields. -- Kind Regards Stephen @ NinjaCoderMonkey www.ninjacodermonkey.co.uk -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
