I'm not sure if I should keep them around or not. The main reason I'm using south at the moment is to ease development changes to the model, though I suppose it will come in handy when I'm in production. Should I be keeping my local development migrations in my Git repository?
我不确定我是否应该保留它们。我现在使用南方的主要原因是为了简化模型的开发变更,尽管我认为它在我投入生产时会派上用场。我应该在我的Git存储库中保留本地开发迁移吗?
2 个解决方案
#1
7
This isn't a technical answer, but if you:
这不是技术答案,但如果您:
- want to roll things back at any stage;
- need to keep a full record of all changes;
- are building up data in SQLite locally and using it remotely;
想在任何阶段回滚东西;
需要保留所有变化的完整记录;
正在SQLite中本地构建数据并远程使用它;
it might be a good idea. Why would you not?
这可能是个好主意。你为什么不呢?
Alternatively, you could maintain a separate branch for the South migrations.
或者,您可以为South迁移维护一个单独的分支。
#2
3
Yes, you should. At some point you won't be able to do schema migration without performing additional data migrations. And those are not auto generated.
是的你应该。在某些时候,如果不执行其他数据迁移,您将无法执行架构迁移。那些不是自动生成的。
#1
7
This isn't a technical answer, but if you:
这不是技术答案,但如果您:
- want to roll things back at any stage;
- need to keep a full record of all changes;
- are building up data in SQLite locally and using it remotely;
想在任何阶段回滚东西;
需要保留所有变化的完整记录;
正在SQLite中本地构建数据并远程使用它;
it might be a good idea. Why would you not?
这可能是个好主意。你为什么不呢?
Alternatively, you could maintain a separate branch for the South migrations.
或者,您可以为South迁移维护一个单独的分支。
#2
3
Yes, you should. At some point you won't be able to do schema migration without performing additional data migrations. And those are not auto generated.
是的你应该。在某些时候,如果不执行其他数据迁移,您将无法执行架构迁移。那些不是自动生成的。