<p>+1 for the jira issue</p>
<p>DROP TABLE doesn't solve the problem at all because generally the view already exists and you willl get an error when schemmaexport intents to create the homonym table</p>
if the view already exists you are unit testing an existing DB...that's not good. You start from a blank DB and create all the entities. If you start with a blank DB as it is needed for unit tests, then the view doesn't exist.
hooray for the new feature :)
Will Shaver has proposed a way to specify what not to export
nhjira.koah.net/.../NH-1274
The SchemaAction.None is nice, but it looks like it does not work in case when a class has many-to-many mapping - the SchemaExport is trying to create the association table even though the owning class has SchemaAction.None set. I have problem with this when using same tables to map to two classes currently - SchemaExport is trying to create the association table twice which results in DB exception because the table already exists..
