我有了一个网络应用(在Pylons)。 我需要有效地改变图象,以便能够至少每天改变生产版本,但可能更多,而不失去数据。
I have played a little bit with sqlalchemy-migrate over the week-end and I would say that it gave me a bad impression. First I think it cannot help with migration between two databases engines; that s something that could probably be done with sqlalchemy alone. Second the docs do not seem up to date. I had to change some command-line options, like giving the repository path at each command, this could be a bug of migrate.
但是,最糟糕的是“管理......pytest”指挥。 不仅如此,它实际上还更新了数据库。 (这一点在文件中有清楚的说明,因此我可以责怪移民),但我的第一份移徙描述只是简单地 st住了化学移民,使经过升级的b带与原来的<different schema相比。 但是,“manage.py”测试只是回答了类似情况。
success !
That is, it did not even check if the schema was left in a coherent state. So is it worth using migrate? Is there any advantage compared to the Do It Yourself method associated with good practices as proposed by S.Lott ? Are there alternatives to sqlalchemy-migrate actually simplifying the migration process or am I just trying to use migrate with a bad a priori (then please show me why is t clearly superior to creating CSV columns as proposed in the link above)?
很多 感谢!