I think this may be it. The document you pointed out says the following: "Adding extra Manager methods is the preferred way to add "table-level" functionality to your models. (For "row-level" functionality -- i.e., functions that act on a single instance of a model object -- use Model methods, not custom Manager methods.)"
The data retrieval logic I was referring to, won't, most of the times, be either "table-level" nor "row-level". It may collect data from several tables and create model objects of several types in a single search operation. However, if not a perfect solution, it seems at least like a step in the right direction. I'll look into it better. thanks, Filipe --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
