lcaamano wrote:
> We're not using Django yet but I think I have a good idea of how we'd
> use it in our framework. I'll try to summarize that in a few
> paragraphs, which hopefully will give you another idea of how to deal
> with the problem you present.
>
> We use two modules per table, one has the "manager class" and the other
> modules has the bare model class and the "managed class." For example,
> if the name of the table is "servers", we then have serversmgr.py and
> servers.py.
>
> [...]
> As you can see, this framework keeps the model completely bare and
> separates logic between the manager (list) and managed (validator)
> classes allowing the view to use the managers as the first point of
> contact.
>
> I'm sincerely curious to know what you guys think about this framework.
Manager pattens remind me of Java. Here's the problem I've seen there.
Manager classes become huge ("Hey, I'll just add getByFoo and we'll be
sweet") and they *still* get in the way when it comes to either schema
evolution, or doing something unexpected but useful real quick.
Which is to say in Java land we used to start with manager classes and
wish for generic DB APIs (like, we did that for *years*, until
Hibernate/Ibatis came along). I've never seen any interesting db-backed
app not need to go round Managers eventually to get something done, ergo
DB APIs rock - and if things crystalise you can refactor the call into
the Manager. But given the quality of DB apis these days, I wouldn't
start with Managers.
So, imo, do what Adrian said and if you can't see the model anymore,
create a Manager class to organize the code (that's what OO is for
ultimately). At that point I think to be idiomatic and consistent across
your domains, put the Manager inside the Model:
class DomainModel(models.Model):
# fields
class Admin:
pass
class Meta:
pass
class Manager: # 'logic' funkiness here
pass
my 2c
cheers
Bill
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
