Is this a good idea? I just starting with FluentNHibernate, and it seems like a good idea for an MVC 3 application. That being said, it appears that you can essentially accomplish the same thing using the FluentNHibernate ClassMap derivatives. If that is the case, would it make sense to create an IDatabase interface with Insert, Update, Fetch, etc. functions and just apply that to the Map classes?
Part of the reason for me asking this is that I wrote a database wrapper for MySQL which has common functionality applied to it (Insert, Update, Delete, etc.), and I'd hate to see that go to waste. I'm beginning to wonder if a Database wrapper is even needed at all.