You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys,
a few weeks back we started using ebean-migration and encountered a few issues. For issues I'd classify as bugs, I've created issues in the ebean-orm/ebean-migration repository here and here and for a question about how to generate a rename migration, I've created a discussion here, but none of these has received any attention. Could you please have a look at those?
Thank you and best regards.
The text was updated successfully, but these errors were encountered:
Ok, I think we can probably close this one now. People can refer to the linked discussion for the details ...
TLDR Table rename and Column rename migrations are intentionally not automatically generated because they are "breaking changes". For these cases we need to do them manually [create the migration xml and sql manually] and understand we need an outage to roll out those migration changes.
Hi guys,
a few weeks back we started using ebean-migration and encountered a few issues. For issues I'd classify as bugs, I've created issues in the ebean-orm/ebean-migration repository here and here and for a question about how to generate a rename migration, I've created a discussion here, but none of these has received any attention. Could you please have a look at those?
Thank you and best regards.
The text was updated successfully, but these errors were encountered: