3 ms·
The post doesn't mention Django's migration system, which is a killer feature. Of course, one should change their database infrequently and deliberately, but it
by heydenberk 7y ago
The post doesn't mention Django's migration system, which is a killer feature. Of course, one should change their database infrequently and deliberately, but it is nonetheless a delight to use, and a feature that is not matched by many other web frameworks, Python-based or otherwise.
- mythrwy 7y agoFlask-migrate for SQLAlchemy (using Alembic) I find every bit as good as the Django migration scheme. I'm not familiar with frameworks other than these two, but I bet Alembic works well in most cases if they don't have something already.
- collyw 7y ago> Of course, one should change their database infrequently and deliberately, I think this attitude leads to a lot of crappy code. It's "safer" just to add a bit more to the application layer than to change the database, but do that enough times and you end up with a mess to compensate for a database design that doesn't model what it needs to. (Learned through experience).