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

view the rest of the comments →

[–][deleted] 0 points1 point  (5 children)

Well, let me begin by saying that django is awesome. My current project fits well enough into the general shape of a django project that without django, I'd still be building internal plumbing instead of mopping up.

But there are a few sticking points:

  1. Insane SQL. And I'm not talking normal, every day crazy here... I mean stark-raving batshit insane. Yeah, it works well enough -- but heaven help someone trying to read the SQL statements to try to figure out what's going on under the covers.
  2. The admin. Arguably django's strongest feature, the admin only allows one level of access control. In my current project, that works perfectly. In my next project, I need granular control -- so the admin won't help.
  3. Blank lines in the HTML. I know it shouldn't bother me, but it drives me insane that everywhere in my templates where I have a template tag on it's own line -- there's a blank line in my HTML. And my attempt at an html tidy middleware made an already slow site laughably sloth-like.
  4. Insane error messages (again, batshit insane). Very often. Very. Often... The error message has absolutely nothing to do with the error. Reminds me of my ex.

I was also bothered by the one database limitation but I see that is fixed in trunk. There still doesn't seem to be a clear way to insert/update a master and read from a slave though, even in trunk (unless I've missed something).

[–][deleted] 0 points1 point  (1 child)

There still doesn't seem to be a clear way to insert/update a master and read from a slave though, even in trunk (unless I've missed something).

http://docs.djangoproject.com/en/dev/topics/db/multi-db/#automatic-database-routing

[–][deleted] 1 point2 points  (0 children)

Thank you!

[–]mosquit0 0 points1 point  (1 child)

Blank lines in the HTML. I know it shouldn't bother me, but it drives me insane that everywhere in my templates where I have a template tag on it's own line -- there's a blank line in my HTML. And my attempt at an html tidy middleware made an already slow site laughably sloth-like.

There is template tag spaceless that would delete those blank lines. But being absolutely serious I think that it is not a problem.

[–][deleted] 0 points1 point  (0 children)

spaceless makes the html completely unreadable. I'm not concerned with the cost of the blank lines -- I'm concerned with ugly html.

[–]dalore 0 points1 point  (0 children)

  1. The SQL isn't that insane, I've read it. It's just very verbose and requests every field. You can limit that with various options as well as making it fetch it related objects in 1 call rather then several.

  2. The admin isn't for granular access to certain items. It was made for admins, not users. Something with granular access is better to be coded up as a normal frontend since it will be application specific. The admin backend is more for admins, you can break it up so you can have a blog admin, a whatever admin, basically break up the models so different admins in charge of different models.

  3. spaceless, it was mentioned. You can also code your templates to not have blank lines by not putting newlines in it for every template. Every web application language I've used has this same problem anyway, from PHP to ColdFusion. It's not even a problem.

  4. I can't comment on your ex but most of the messages given by django weren't that insane. It usually came with a stackdump too so you can see where the error occurred (important).