As I recall, Django does give both options and can be confusing. I went from Django to turbogears, and personally, SQLObject is much more intuitive and more pythonic.
While there may be features in Django that we might want to look at, (auto-crud, generic views (generic controllers and templates), etc.) but I don't think there is much in Django's ORM "to write home about" (at least compared to SQLObject). Again, this is my personal view, but Django's model is part of what made me leave Django for TG. If I could remember any details about Django's models I would mention them, but I guess this just means that is was not that remarkable. Sorry to be negative. I hope there is something constructive in here. I'm sure others will have differing opinions. Krys Kevin Dangoor wrote: >On 10/26/05, Todd Greenwood <[EMAIL PROTECTED]> wrote: > > >>Great, thanks Kevin. I'll put this in my next tutorial extension. >>Somehow this escaped me in the docs. The django has an OR mapping more >>like what I was expecting... >> >> > >Which is? > >I'm all for API improvements that make things easier. I haven't >studied Django's OR mapper in enough detail to know where it's better >or easier, so it's good to hear from people who've actually used both. > >In this particular case, it may actually be confusing to have an >addEntry method. Consider this: > >p1 = Page(..) >p2 = Page(..) >e = Entry(page=p1) >p2.addEntry(e) > >So, what happens there? Does e's page change to p2? > >Since you *have* to specify a page when creating an Entry, the >relationship is dealt with. > >Kevin > >-- >Kevin Dangoor >Author of the Zesty News RSS newsreader > >email: [EMAIL PROTECTED] >company: http://www.BlazingThings.com >blog: http://www.BlueSkyOnMars.com > > >
