On 3/14/06, limodou <[EMAIL PROTECTED]> wrote:
> On 3/14/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> >
> > On Tue, 2006-03-14 at 09:34 +0800, limodou wrote:
> > [...]
> > >
> > > -1 I agree with gabor. Many orm models don't process validation, and
> > > these things should be implemented by manipulator. Why do so much
> > > things in model?
> >
> > This isn't really an argument, though. Other systems working differently
> > is not a reason why Django should not work in the way Adrian described
> > ("other systems are not blue like this, they are red. So blue is no
> > good.") Why do you see it as bad that it should work this way? What are
> > the arguments against doing this in the model (which is a representation
> > of the data structure and so not a completely illogical place to work
> > with the data)?
> >
> > Malcolm
> >
>
> because I think manipulator can be standalone separated from the model
> and maybe someday the orm can be designed as an interface, so that we
> can use other orm module to replace django orm.
>
> If you don't want, and the model becames more and more rich, so these
> things maybe not be separated any more.
>
I like django, and I'm learning hard on it. But someone don't like
django, and they don't like django orm, they like sqlobject,
sqlalchemy. So if the db api is really loose and replable, we can drag
them back to django.
I don't know whether there is a such plan in django team.
--
I like python!
My Blog: http://www.donews.net/limodou
NewEdit Maillist: http://groups.google.com/group/NewEdit
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
