The mapping that I am trying to create would be a lot easier if I could map to a view instead of to a table for one class that I have. The Hibernate documentation and groups say that hibernate doesn't know the difference between a view and a table. Is this true with NHibernate, or are my troubles limited to my firebird database?

I tried mapping to a view and NHibernate told me that the table was invalid. I then dropped the view and created a table in it's place and the mapping worked, so there obviously isn't anything wrong with the mapping other than that the underlying schema needed to be a table instead of a view.

To prevent some questions: My test performed only a simple read, i.e. CreateQuery("FROM TableX"), so it should have nothing to do with the insert or update capabilities of the view/class.

We map to views now, and it works for simple stuff. Unless the view has primary keys defined, relationships are hard, but that's what the view is for.

For small stuff, it works. As your project grows, it sucks big time.