3 ms·
The problem I have with Django, is that it tries to micromanage the database table for me with its own flavor of ORM. To get around it, and not use ORM, and bu
by blackrock 6y ago
The problem I have with Django, is that it tries to micromanage the database table for me with its own flavor of ORM.
To get around it, and not use ORM, and build out the tables yourself, is difficult. The documentation examples appear to be lacking.
I don’t have a problem with writing my own SQL queries, or writing my own table creation query code, but I tend to have problems trying to get Django to work with my custom tables. Mostly because the documentation doesn’t seem to be geared around doing that.
And then, some people say, that if you’re not using the Django ORM, then there is little point in using Django anyways, and you should use something more lightweight like a Flask.
Maybe someone else with more Django experience can chime in here.
- GlennS 6y agoI don't have loads of Django experience, but I have done some Django and some raw SQL + Flask and had good experiences with both. I think I agree with you. A lot of the benefits that you get from Django and its plugin ecosystem come from having the models available as a common representation of the database that you can be transformed and inspected by various other tools. If you don't want to use Django models, then I think Django is the wrong option. Flask is a pretty great option. FastAPI adds some stuff that I really like and does it well, but is still only a year or two old, so might be too risky for some projects.