On Fri, Mar 19, 2010 at 11:09 AM, Karen Tracey <[email protected]> wrote: > 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.
I agree with this sentiment. To me, the example API shown here reads almost just like SQL. There's already a mechanism for writing raw SQL, and the example provided doesn't seem to be a whole lot simpler. Maybe a solution is some extension to django.db.connection that would let you get back objects with named fields (or maybe just dicts) in place of plain tuples? You'd get all the flexibility that you want, but more readable code (accessing field names rather than sequence indices). Taylor -- 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.
