I'm developing a big application that does some complex mixing of database: SQL and notSQL one. I'm using the multidb to manage all the stuff in a django manner, using routing to route items in MongoDB and Postgresql.
Some bugs that I've discovered: 1) django is unable to manage different Autofields from integer ones. A patch is to extend the BaseDatabaseOperations to manage different types from default one. (Patch available here: http://github.com/aparo/django/commit/62baf86ff872b3a271619a4327d7b08180c89337) 2) the mixing of foreignkey in different backends are not managed correctly (there is a note on documentation on multidb page). A patch that check convert the type of foreign key with expected type is here: http://github.com/aparo/django/commit/edcdc1d9364224fcbc3b810b9d9fa19a10cd537c only the modification to related.py is important. 3) foreign key search and saving in different backends are buggy due to "hints" caching. Disabled cache choose of database on instance (http://github.com/aparo/django/commit/b1c8478f45997df22b3a477c8d3f382613d69246) 1-2) depends that mongodb use string as autofield type 3) django calls the wrong backend if no route is specified for a model and not the default one. Do I need to open a ticket on trac to commit these patch or we need first to discuss them? Regarding support to nosql engines, we are able to mix a lot of models between mongodb and postgresql using are backend engine (http://github.com/aparo/django-mongodb-engine) that works also on the current trunk django 1.2 and using routing massively. I think that there are datamodels that works very well on nonrel db and other that are only suitable for sql: it depends on designer to choose the good solution for a problem. Congratulations for the 1.2 release. Hi, Alberto Paro -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
