2 ms·
Many times when I’d like to use Django, I have to eliminate it because of one thing: I’d like to access the database from non-web programs, and Django certainly
by teddyh 12y ago
Many times when I’d like to use Django, I have to eliminate it because of one thing: I’d like to access the database from non-web programs, and Django certainly does not make it easy to use its ORM in a non-web context.
Sometimes I’d even like to access the database from external, possibly non-Python tools, and then Django is out of the question, since it does not define a stable API to its database layer, only its ORM.
Therefore, I go with Flask + SQLAlchemy in these cases.
(One time, for a short-lived project, I chose to ignore that Django does not provide a stable database, and simply let Django create the database and then simply assumed that the database table definitions would not change during the lifetime of the project and accessed it externally via SQL. But this was for a short-lived project which would only run for a few days.)