Hi
I while ago, I read a artikle in Dr.Dobbs, that stated that every table in a database should at least hav 4 columns, CreatedBy, ModifiedBy, CreatedDate and ModifiedDate. After that, I noticed from other writers that that statement is accepted as best practice.

Taking this into accont,, is there a "best way" to implement this when using NHibernate??




//regards
//lasse
//NHibernate newbe

we implemented a class named ModifiedInfo and mapped it as component to each table. The we use the IInterceptor interface to implement an interceptor which sets the values of the fields. There is a sample in the NHibernate documentation. See http://www.hibernate.org/hib_docs/nhibernate/html/manipulatingdata.html#manipulatingdata-interceptors

Regards
Klaus

Personally, since I often have my domain running at several remote locations from the database server and I like to keep the date/times synched with the database server I open a new connection in my interceptor and execute GETDATE() against the db to get the current date/time from there before updating the entities.

Causes a performance hit, but it's worth it for me.

Cheers,

Symon.

This seems like a way to go, still I have a couple of questions. If I have a many-to-many relationship, will the "mapping table" also be updated, using this interface?? How to you specify the many-to-many relationship to contain columns for ModifiedInfo data.

//Regards
//Lasse

Assosciations will only be flagged as dirty if they have been modified. If you implement your interceptor similar to the one in this posting http://forum.hibernate.org/viewtopic.php?t=971049, anything that is dirty and implements the proper interface will get trapped and have its info updated.