Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

At work we use Django migrations. It helps. But the core of schema evolution is backward compatibility. To reach this goal, code review is necessary.

Here we never drop columns, only add new colunms, also never change column types.

When it comes to constraints (not null or something else) we double check about backwards compatibility.

Changing data is not a robust rollback.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: