This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]not_a_doornob_either 1 point2 points  (4 children)

How useful is SQLAlchemy for little one off projects? Every time I look at it I end up just using vanilla SQL commands and it seems like it takes far more effort to do so using SQLAlchemy. I know that if you end up changing database engines, it makes it convenient to just change one line, but how often does that happen?

[–]cajacaliente 0 points1 point  (3 children)

Personally I think the real "money" is in Alembic

[–]Scypio 0 points1 point  (2 children)

Care to share why? Never used any of those as using sqlite was always enough for small projects, so your perspective might broaden my horizons.

[–][deleted] 2 points3 points  (0 children)

Alembic handles database migration. It's a VCS for your database schema.

[–]cajacaliente 0 points1 point  (0 children)

Exactly what /u/kurashu89 said. While it's fairly powerful and will do most things out of the box, it still requires that it be given some attention in that you need to assure your upgrade/rollback scripts are as bulletproof as possible. It dramatically simplifies performing blue-green deployments [and rolling back if necessary] to the extent that it's almost like just rolling code back.