Good question, I just completed an exercise removing unnecessary "created" fields in similar sounding app configuration models like categories etc. Like yourself, done in the hope of squeezing out a bit more performance and simplification, but not really based on objective fact if I'm honest.
Your point about modified possibly influencing caching is a good one, if you find out please let us know on this thread! What I would say is, do review your mysql DB schema; careful use of additional indexed fields in my experience can have a considerable positive effect with this sort of model, especially where your configuration model tables have other attributes that you search (find) on. I have stuff like "enabled" fields so i can retire old options but maintain historic reporting, I often need to pull all the rows where enabled="1" if you see what I mean, so an index here can be beneficial I think. On 11/11/08 23:10, Zoltan wrote: > Just wondering about if there's any performance or other reasons to > include created / modified fields in tables that probably don't change > much? > > I have a table called 'categories' that has : > id (tiny int unsigned) > name > created > modified > > Now the table has about 50 items in it and I'm trying to keep it > pretty small to hopefully catch a mySQL performance boost and I'm > wondering if it makes sense to include the created and modified > fields-- would cake do any kind of caching automatically that I'd be > missing out on? > > Zoltan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
