Hi, If you want to log crud actions on your models, just add them a listener (look at the Doctrine doc about Doctrine_Template and its Loggable behavior).
The event system is good when you want to do something else, from somewhere else. Before Printing, Think about Your Environmental Responsibility! Avant d'Imprimer, Pensez à Votre Responsabilitée Environnementale! On Fri, May 14, 2010 at 8:14 PM, f1gm3nt <[email protected]> wrote: > So I'm faced with the problem of logging CRUD.... > > So if a user saves a form I need to insert information into a > database. Right now I'm thinking that the symfony event system will > work best. I've been playing around with it and so if a form is saved > then if it's new, then it will notify 'object.create' and if the form > is being updated then it will notify 'object.update'. > > This seems like the most logical way to do this and I have a table in > the database that stores this information. Has anyone else ever done > this or can someone give some insights? > > -f1g > (Hi Boss ;p) > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en
