Should I keep my southern migrations in version control?

I'm not sure if I should keep them around or not. The main reason I'm using southat the moment is to ease the changes in model development, although, I believe, it will be useful when I'm in production. Should I keep local development migration in my Git repository?

+5
source share
2 answers

This is not a technical answer, but if you:

  • Want to return data at any stage;
  • you must save a complete record of all changes;
  • collect data in SQLite locally and use it remotely;

that might be a good idea. Why do not you want?

.

+7

, . - , . .

+2

All Articles