News for hackers. Stuff that matters.

A comment on Django vs. Flask. Parent comment

Re:Django vs. Flask by jedberg on Monday July 03, 2017 @03:46PM (#14690872)
Mostly the ORM. If you rely on it, you can't really lay out your tables in any way except the way they do it, at least not without a whole lot of headache.
[ Parent | on HN ]
Re:Django vs. Flask by njharman on Monday July 03, 2017 @05:13PM (#14691447)
It requires you have a primary key. That's it.

Everything else table names, fk's, multiple databases, etc. is overridable. The only thing I know of that is a slight headache is postgresql namespaces (aka schemas).

Django does make choices for you. But almost everyone of those choices can be overridden. I have found that most people who think Django (or any large/mature/widely used project) can't to something is because they don't know it well enough.

[ Parent | on HN ]
Re:Django vs. Flask by tedmiston on Wednesday July 05, 2017 @12:40PM (#14703915)
Not sure what you mean by this. You have full control over your table schemas and relationships with the Django ORM.
[ Parent | on HN ]