I left django after a while as it is doing too much, some of it in the wrong way. The ORM will generatie terrible queries, so you end up writing all of them yourself, also database models never fit use-cases, so ORM's are almost always another level of no-abstraction. Role-management goes on top of the RDBMS roles, which is doing things twice and probably less well than your RDBMS. Forms and templates are OK though, but not worth the effort of going through python-pain. The best feature is that it will adapt to an existing database, greenfields are an exception and django is good in adapting to existing stuff. The migration features are useful only if django is the only way to access data. It never is, so migration normally is addressed at the database level with backwards compatibility.
Yes Joost, you're absolutely right. I found myself having to work-around the opinionated-batteries-included framework several times because it either didn't do what I needed or did it in a clumsy time consuming way to implement. I was fundamentally appalled at the crazy queries it generates.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I left django after a while as it is doing too much, some of it in the wrong way. The ORM will generatie terrible queries, so you end up writing all of them yourself, also database models never fit use-cases, so ORM's are almost always another level of no-abstraction. Role-management goes on top of the RDBMS roles, which is doing things twice and probably less well than your RDBMS. Forms and templates are OK though, but not worth the effort of going through python-pain. The best feature is that it will adapt to an existing database, greenfields are an exception and django is good in adapting to existing stuff. The migration features are useful only if django is the only way to access data. It never is, so migration normally is addressed at the database level with backwards compatibility.
Yes Joost, you're absolutely right. I found myself having to work-around the opinionated-batteries-included framework several times because it either didn't do what I needed or did it in a clumsy time consuming way to implement. I was fundamentally appalled at the crazy queries it generates.