On 14 juin 2015, at 20:23, [email protected] wrote: > It would only be worthwhile trying to make a proper database-engine if the > rest of django would support it: Specifically, any kind of data modification > using SQL is currently unsupported
This is an well defined limitation. If you can make the ORM work for read queries, some might find it useful, even if write queries don’t work. > and JOIN queries requires one of the sides to actually be a PK. I believe Django only generates such joins, so you’re safe. That said, in my view, the Django ORM is a series of layers that bridge the gap between a document-oriented API and SQL. I find it weird to shoehorn NoSQL databases into this framework when they already have a document-oriented API of their own… An important part is to manage connections properly (I’m not sure what’s adequate for Couchbase) and to provide a solution to run tests (create a test database for tests, drop it when tests are finished). If you implement a database backend, you get this for free. Otherwise, you have to manage it yourself. Here’s a project that does this for ElasticSearch: https://github.com/Exirel/djangoes <https://github.com/Exirel/djangoes> I hope this helps. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/67AB5D70-975E-4B2F-9AFA-52CA585072FD%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
