On 5/15/07, Vertigo <[EMAIL PROTECTED]> wrote: > I could build a custom method (get_public_documents) on model Project. > But the documentation suggests that model methods are 'row-level' > oriented.
And yet the methods which fetch the set of related objects are instance methods, not class-level manager methods ;) The "row level" distinction basically means that things which deal with one single instance of your model class should be instance methods, and things which deal with your entire model class as a whole should be manager methods. Retrieving objects related to a single instance -- even with filtering -- is something that deals with a single instance of the model it pertains to, and so should be an instance method. And even then, it's mostly a guideline for helping you keep your code organized, not an absolute rule. So go ahead and write a "get_public_documents" method (though for consistency with how Django names the automatic related stuff, I'd personally be more likely to call it "public_document_set") and don't feel bad about it. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
