Re: Template: nested for and ManyToMany field problem - MySQL

> Then you want entry.categories.all in your template. That was the problem. Thanks. -- Adam Hoscilo --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group,

Template: nested for and ManyToMany field problem - MySQL

remove the nested for everything works fine. I tried to fetch entries with .select_related() and without - no difference. Database backend is MySQL 5 Anyone had a problem like this one? -- Adam Hoscilo --~--~-~--~~~---~--~~ You received this message because you are

Re: Custom manager filter by logged in user.

Not that way anymore. I will just check (in the middleware) if the requested entry's author is the logged in user (for edit action) if not throw exception. -- Adam Hoscilo --~--~-~--~~~---~--~~ You received this message because you are subscribed to the G

Re: Custom manager filter by logged in user.

You're right - my fault. It just isn't the way I would like to handle this problem. But I've forgotten about middleware and I think this will be the best way to solve this _issue_ without breaking MVC(MVT) schema (just check if the requested object was created by user). --~--~-~--~~-

Re: Custom manager filter by logged in user.

But it's some kind of a hack that I don't want to have in my app. It's easy to achieve this by get/filter in views - but manager would be more secure(error-proof). -- Adam Hoscilo --~--~-~--~~~---~--~~ You received this message because you are su

Custom manager filter by logged in user.

anage that by custom managers or maybe some other nice way? PS django.pl coming soon :) -- Regards Adam Hoscilo --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group,