Comments on: Symfony exceptions, logging, and debugging http://stereointeractive.com/blog/2007/06/12/symfony-exceptions-logging-and-debugging/ Development Blog Thu, 17 Jun 2010 09:37:20 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Steve B http://stereointeractive.com/blog/2007/06/12/symfony-exceptions-logging-and-debugging/comment-page-1/#comment-359 Steve B Mon, 05 Jan 2009 17:11:50 +0000 http://blog.stereodevelopment.com/2007/06/12/symfony-exceptions-logging-and-debugging/#comment-359 Hi, Thanks for the very helpful but simple post. With regards to logging messages in the database, I'm pretty sure you'd be able to extend the sfLogger class or something to do this. Not sure how at the moment, but I understand symfony enough to guess this would be achievable! Steve Hi,
Thanks for the very helpful but simple post. With regards to logging messages in the database, I’m pretty sure you’d be able to extend the sfLogger class or something to do this. Not sure how at the moment, but I understand symfony enough to guess this would be achievable!
Steve

]]> By: Scott Meves http://stereointeractive.com/blog/2007/06/12/symfony-exceptions-logging-and-debugging/comment-page-1/#comment-298 Scott Meves Mon, 15 Sep 2008 15:34:44 +0000 http://blog.stereodevelopment.com/2007/06/12/symfony-exceptions-logging-and-debugging/#comment-298 Hervé, If you want to log actions in the db when executed, I wouldn't even use the sfLogger class and instead just add custom code to my objects save() methods. A propel behavior would be perfect for this kind of thing!!! I would take a look at some of the <a href="http://www.symfony-project.org/plugins/filter?filter[sf_1_0]=on&filter[sf_1_1]=on&filter[sf_1_2]=on&filter[propel]=on&filter[doctrine]=on&filter[category_id]=4" rel="nofollow">existing plugins that provide propel behaviors</a> and then just dive in and write your own. It'd make a great plugin ;) -Scott Hervé,

If you want to log actions in the db when executed, I wouldn’t even use the sfLogger class and instead just add custom code to my objects save() methods.

A propel behavior would be perfect for this kind of thing!!! I would take a look at some of the existing plugins that provide propel behaviors and then just dive in and write your own. It’d make a great plugin ;)
-Scott

]]> By: herve http://stereointeractive.com/blog/2007/06/12/symfony-exceptions-logging-and-debugging/comment-page-1/#comment-297 herve Mon, 15 Sep 2008 13:36:48 +0000 http://blog.stereodevelopment.com/2007/06/12/symfony-exceptions-logging-and-debugging/#comment-297 Hej, I am wondering: how could certain actions be logged in the db when executed? I d like, for instance, the save() actions of certain modules to be logged in the db to create an history table of what happens on the site. Except creating an history table and saving the informations I am interested in in every actions, The info logs don't seem to be reusable. Could a propel behavior do that? Cool reading you, mvh, hervé Hej, I am wondering:
how could certain actions be logged in the db when executed? I d like, for instance, the save() actions of certain modules to be logged in the db to create an history table of what happens on the site.

Except creating an history table and saving the informations I am interested in in every actions, The info logs don’t seem to be reusable. Could a propel behavior do that?

Cool reading you,
mvh, hervé

]]>