On 10/10/2011 04:59 PM, Anssi Kääriäinen wrote:
In the perfect world you could have a SQLA backend, or qs.as_sqla() method. That would be neat, yes. QuerySet chaining could be hard to implement, though (or does SQLA have support for something like that?). But in my opinion this is another argument for refactoring the ORM. When the ORM has better separation of concerns and better abstractions between compiler and sql/query.py it will be easier to write different compilers - be it a compiler for Cassandra or SQLA.
What's required to make different database backends easy are correct abstractions -- currently the ORM backend abstraction is pretty messed up, at least it's not written with non-SQL backends in mind.
/Everything/ SQL related should be moved into a base SQL backend. The code in django.db.models should be completely query language/database agnostic. Currently, SQL generation is scattered over multiple places and abstraction layers, django.db.models.sql.* and django.db.backends etc.
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
