We have converted an existing login system to use NHibernate but have hit a problem:

It turns out that there are 2 versions of an application using this code in production using 2 different versions of the security database. This is acheived by having 2 copies of the database with different names. Previously there was a security database specific connection string, so this could be adjusted on a app by app basis. Now however, we are using the schema attribute in the security specific mapping files to specify the database name.

Unfortunately we have already used the default_schema attribute in the app config file to point to another content database.

So the question is, does anybody know of a way to switch the schema for a particular group of class mappings at runtime? Or any other way we could address this?