On Feb 9, 2008 8:45 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I see. Not the way I would do it to be honest, but it's possible... > > What you really want to do is avoid overriding the save method in the > model and use either a beforeSave hook in the model, or writing a > behaviour (1.2) that has similar beforeSave hooks in it. > > I would watch that column quite carefully if I were you, a few updates > and, and you could quickly find yourself with very sub-optimal > database row lengths.
Thanks, the data does not change often, and after (say) 30 days the history is truncated. Were I to use beforeSave, roughly how would I got about it? I mean, what do I need to do before/after the "history" logic? -- Ben Wilson "Words are the only thing which will last forever" Churchill --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
