On Wed, Feb 24, 2010 at 7:57 AM, Russell Keith-Magee <[email protected] > wrote:
> On Wed, Feb 24, 2010 at 12:20 AM, P.R. <[email protected]> wrote: > > Hello, > > > > I have question about type of design patterns using in Django ORM. It > > is: Table Data Gateway, Row Data Gateway, Active Record or Data > > Mapper? .. Personally I think that it's mix of Row Data Gateway and > > Data Mapper, but I want to ask You guys for sure :-) > > Honestly, I have no idea. The ORM wasn't constructed as an > implementation of a design pattern; we just built an API that made > sense. > > Yours, > Russ Magee %-) > :-) The Django ORM doesn't follow any of the EAA patterns exactly, and I don't think that it makes sense trying to force the design patterns names on it. Just because something does a good job at solving a problem it doesn't mean that it has to follow the documented design patterns. This is very similar to trying to force the MVC pattern on Django which also happens a lot. Not every web application framework that separates concerns properly has to be an MVC framework, no matter how fashionable MVC is. It is fine to be MTV :) All The Best, Tamas -- 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?hl=en.
