AFAIK there's no way to tell the Modeler to ignore certain manual model tweaks
when creating migrations. Things like that are the reason why I am using manual
SQL-based migrations to evolve my schema.
Andrus
On Feb 4, 2012, at 3:11 AM, Tad wrote:
> We've got an existing MySQL 5.x database tha
We've got an existing MySQL 5.x database that contains a single view. This
view includes the primary key column of its source table in its results.
When modeling this view with a db-entity (through re-engineering,
migration, and manual creation) the modeler tells us that the entity lacks
a primary
