Not sure how the migration tool determines the diff, but at least in Postgres if the dbentity schema doesn't match the database schema Cayenne cannot find the table in the database and will drop it.
When I added the schema 'public' to the dbentity Cayenne' diff worked properly. kind regards Bob On Tue, Aug 14, 2018 at 9:36 AM Andrus Adamchik <[email protected]> wrote: > The modeler migrate schema functionality is not sophisticated enough for > production workflows. So I suggest Liquibase for migrations and DB-first > approach to ORM. > > Andrus > > > > On Aug 14, 2018, at 12:07 AM, Tony Giaccone <[email protected]> wrote: > > > > I've made some changes to the schema on a project I'm working on. I > > selected Migrate Schema, and worked through the Wizard and in the end it > > wants to drop tables. Some of my tables are rather large, and recreating > > them would be... painful. Is there a way to find the diffs that the > model > > identified, as opposed to the drop table that it suggested? > > > > Any suggestions? I can of course figure out the differences by hand the > > number of tables is small, only 5.. but I'd like to understand how the > > modeler decides what path to take when it sees diffs. > > > > > > Tony > >
