On Fri, Mar 19, 2010 at 10:47 AM, Jacob Kaplan-Moss <[email protected]>wrote:
> On Fri, Mar 19, 2010 at 7:39 AM, Sh4wn <[email protected]> wrote: > > I want to refactor the QuerySet and other databases related API's, > > which adds an additional method of selecting records, and provides > > more control of what data you'll select, but probably is a bit more > > complex than the current API. > > I don't want to discourage you, but... > > Wait. > > Actually, I *do* want to discourage you. [snip backwards compatibility > concerns] > It wasn't immediately clear to me that this proposal involved breaking backwards compatibility -- it sounded like it might just involve adding methods and not necessarily changing the behavior of existing ones. However, it does seem to be in direct conflict with the idea of getting to the ORM working on non-SQL databases. The additional methods mentioned (select, from, leftJoin) together all sound like they are moving the app-ORM interface closer to raw SQL rather than away from it. Given the more long-standing interest in getting the ORM working with things like app engine's BigTable, I can't see a proposal for movement more towards raw SQL being accepted. Karen -- 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.
