On Wed, Apr 27, 2011 at 10:12 AM, Waldemar Kornewald <[email protected]> wrote: > Hi, > we (the Django-nonrel developers) would like to work on official NoSQL > support for Django. We'd like to focus only on databases similar to > App Engine, MongoDB, and Cassandra 0.7+ with secondary indexes. Our > goal is not to support all native query features of key-value stores > like Redis.
Did you guys consider providing a Document class that is entirely separate from models.Model? Technically speaking teaching the ORM non-relational tricks is of course possible but in reality the philosophy is entirely different and you need to plan for NoSQL from the very beginning. Traditional models are flat and have a schema, NoSQL documents can have extra fields and each of them can hold a fairly complicated structure, possibly involving numerous other (python-enforced) schemas at different points in the tree. In the end you won't be able to move models or logic between traditional RDBMS and NoSQL engines anyway. What we get instead is either a whole bunch of NotImplementedErrors or a heap of hacks to simulate traditional relations in a world that does not need them. Of course as much of the ORM API as it makes sense should be supported by the Document but I really feel these should be designed as separate object types. -- Patryk Zawadzki I solve problems. -- 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.
