On Jun 19, 5:59 pm, James Bennett <ubernost...@gmail.com> wrote: > On Fri, Jun 19, 2009 at 6:49 PM, poop<alex.so...@gmail.com> wrote: > > It is not, but it is not much of a web application framework if it > > doesn't already have a rich set of tools to work with. > > It does. Of course, your issue seems to be not that Django lacks > certain tools, but that it doesn't already provide every tool you > personally need. ... > So as a general rule, the question should not be "why doesn't Django > have this already" -- it should be "can I help to implement it". > Because, really, that's the only way the project moves forward. >
I am not so impressed with Django's features, honestly. Aside from the auto-admin interface, the feature set does not seem any richer than Perl's Catalyst. I don't mean to sound ungrateful. You are right about the correct approach to move a project forward. But it isn't particularly nice to developers to make them learn and muck around in your middleware to perform common tasks. > > I could kill whoever told me Django was great, and forgot to mention > > there's no row-level permissions... > > Judging from your other email about it, I'd suspect you're into the > realm where no out-of-the-box system could be both simple enough to > cover common cases and complex enough to handle every situation people > would like to implement. Which, to me, is fine: sometimes it's just > not possible to produce a "generic enough" system to cover every use > case, which means some folks end up writing custom code. Fortunately, > people who use Django are (at least in theory) programmers who can > evaluate what's needed and get their work done. Heh, I didn't realize Google ever posted my other message. I will be sure to check the responses to it. Thanks for mentioning it. I agree, it is true that no out-of-the-box system would "just work" for me. And I am not afraid to get my hands dirty with programming. But a generic permissions system ought to be a solved problem by now. A search function ought (and apparently is) a solved problem by now. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
