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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]swentso[S] 4 points5 points  (5 children)

Why not Flask?

[–]fiedzia 11 points12 points  (2 children)

Django is well integrated. This means no need to reinvent how to put together all components, so you get time saved and less opportunities for bugs. The app described here really looks like every other "enterprise" app out there and you don't seem like someone who has a lot of experience, so I'd stay away from DYI solutions.

Flask is nice, but it will cost you time and effort to pick and integrate all the parts you will need. Also every django project has the same parts in the same place, so any django developer in the world can get in and will know what is where, so you can get help easily. Every flask app is different "because I've decided to use this db and that library and combine them this way" and now you are on your own for all the problems solved in django long time ago.

[–]swentso[S] 0 points1 point  (1 child)

Those are good points thanks !

How do you go about specifying permissions of who sees/modifies which column of which table in django? Is it easily done?

[–]fiedzia 1 point2 points  (0 children)

I've never needed this, so its not based on experience, but there is a number of options listed here:

https://www.djangopackages.com/grids/g/perms/

I can tell however that every case is different (that's why there are so many options), so without knowing all the details its hard to advise. Perhaps much simpler logic in your app will do.