@
Hello,
I may have found a little problem/bug, working with ODAC 12c R3 Beta 2 and Entity Framework 6. I disabled AutomaticMigrations and use code based migrations instead. When applying changes to my data model without adding a code based migration file, I run into the expected exception. This exception tells me that AutomaticMigrations are disabled and that I have to turn them on or create a code based migration file instead - so far so good.
But this also makes the table __MigrationHistory disappear, which is a not that good in my opinion. I doubt that it would have any impact on the release versions of our application because we will always add all needed migrations before a release, but while developing it can mess up the development database if you accidentally connect to it with a changed datamodel before adding the migration file. I found a workaround to restore the __MigrationHistory by hand but maybe you can look at it and fix it for the stable version anyway. Other providers (MSSQL, MySQL, etc.) also throw the exception but won't touch the __MigrationHistory.