-
-
Notifications
You must be signed in to change notification settings - Fork 68
Open
Description
I have just migrated from play 2.6 and an older version of play-ebean plugin to play 2.8 and version 6.0.0 of this plugin
We have noticed a change of behavior when running evolutions on a dev server
Previous behavior on a working app
- Change a model in any way (let's assume that we change the name of a property)
- Starting the app notifies the developer that an evolution has to be run
- Pressing the apply button results in possibly another error (inconsistent state), and marking the problem as resolved causes the entire database to be deleted and recreated with the new schema
Current behavior
- Pressing the apply button notifies of an inconsistent state
- Continuing to press the button reloads the same page
- After some reloads the max url limit is reached
In the end what i would like to achieve is that when ebean generates a different schema, the entire database is deleted and recreated accordingly.
plouf142 and A-L-Fearon
Metadata
Metadata
Assignees
Labels
No labels