It depends :-) I have some "auditing" done through Hibernate interceptors, some done through triggers, and some implemented in my business layer.
> -----Original Message----- > From: Robin Helgelin [mailto:[EMAIL PROTECTED] > Sent: Friday, August 31, 2007 11:49 AM > To: Tapestry users > Subject: [OT] Business layer or database > > Hi, > > I'm working on an application which will store changes from a few > tables in an audit table for history. However, I'm not sure which path > to choose. > > Should I solve this problem in my business layer, or should I solve > this at the database level using triggers/stored procedures? > > Currently I'm leaning towards database level as the solution will work > even though not accessed from within the business layer. > > -- > regards, > Robin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
