tags:

views:

281

answers:

2

I am using NHibernate's SchemaExport to create my database schema. I have 1 legacy ref table that cannot be recreated with the Schema Export because it is already in use with other apps that use the same DB. Is there any way to map this table but tell NHibernate to skip it when running the SchemaExport?

A: 

Try using SchemaUpdate() instead? it should see the table already exists and not issue a CREATE statement

defeated
+4  A: 

This feature was recently added to the NHibernate trunk (see this message in the NHibernate development mailing list). So if you are using the trunk, you can use the "schema-action" attribute to control the behavior of SchemaExport().

Sean Carpenter