NHibernate技术文章.docVIP

NHibernate 技术文章  NHibernate 技术文章 1 How to use Nhibernate with variable or dynamic table names like Jan08Tran,Feb08Tran,Mar08Tran 3 How to use Nhibernate with variable or dynamic table names like Jan08Tran,Feb08Tran,Mar08Tran I had a similar situation where I had to provide an interface between to purchased applications that were in production and being used by tons of different systems. This system had different table names throughout dev, test, and prod (ridiculous...) My solution was to leave a placeholder for the table number in the NHibernate config like so: class name=MyClass table=MyTable[tableNumber] And then implement INamingStrategy similar to: public class MyCustomNamingStrategy : INamingStrategy{? ? public string ClassToTableName(string className)? ? {? ? ? ? return DefaultNamingStrategy.Instance.ClassToTableName(className);? ? }? ? public string PropertyToColumnName(string propertyName)? ? {? ? ? ? return DefaultNamingStrategy.Instance.PropertyToColumnName(propertyName);? ? }? ? public string TableName(string tableName)? ? {? ? ? ? tableName = tableName.Replace([tableNumber], LocalSettings.TableNumber);? ? ? ? return DefaultNamingStrategy.Instance.TableName(tableName);? ? }? ? public string ColumnName(string columnName)? ? {? ? ? ? return DefaultNamingStrategy.Instance.ColumnName(columnName);? ? }? ? public string PropertyToTableName(string className, string propertyName)? ? {? ? ? ? return DefaultNamingStrategy.Instance.PropertyToTableName(className, propertyName);? ? }? ? public string LogicalColumnName(string columnName, string propertyName)? ? {? ? ? ? return DefaultNamingStrategy.Instance.LogicalColumnName(columnName, propertyName);? ? }} And then set the naming strategy in the configuration: myConfiguration.SetNamingStrategy(new MyCustomNamingStrategy()); This way the table number could be stored in the App.config and the application could be moved across environments by only changing values in the App.config. Im s