0

I'm using Play Framework 2 with EBean and MySQL for the database. When a member of any of my model classes is changed, it creates a db evolution, and play wants to wipe out the old database.

Does anybody know a good process for preserving the old db values when the schema is updated and evolutions are run?

Evgheni Crujcov
  • 470
  • 2
  • 8

1 Answers1

1

You need to start writing evolutions scripts manually, as described here

Assuming you are using the ebean plugin you also need to stop DDL generation via application.conf like so evolutionplugin=disabled

mdell
  • 106
  • 2