sql - DB Evolution in Play Framework 2.0 -
On Play 1.0, when we change a variable type or for example @OneToMany change @ManyToMany to model play Make changes automatically, but with the 2.0 development script drop-down database. What is a way to apply the changes without leaving DB to Play 2.0?
Yes, one way. You need to disable the automatic reconstruction of the file In practice it means that, if you are working with a single database then you can also ... Manage the database tables and columns using your favorite DB GUI Evolutions Only when you are unable to use the GUI (host external connection is not allowed and do not have any GUI) or when you are planning to run multiple instances of the application on different databases, otherwise the GUI can be used. Yoga manually typing will be manually more complex. Tip: Sometimes, if I'm not sure if I have added all necessary relationships and barriers to my manual evolution, then I'm removing this Git Controlled Folder!) And with the Abine Plugin Turning the app on and saving the proposed 1.sql and start writing your own evolutions with
ALTERS instead of
CREATES - them
2.SQL ,
3.sql etc.
1.sql , but I am not implementing changes later on using GIT, I am changing my evolution and saved auto-generated savedI'm comparing the Hail and
would like to make to convert ALTERS statement. There is no better option for managing changes without using 3-rd Part software.
Comments
Post a Comment