On Tue, May 18, 2010 at 5:08 PM, Alberto Paro <
albert...@gmail.com> wrote:
> 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:
As a point of order, when something we don't support doesn't work,
it's not a bug - it's a feature request.
In this case, what you're actually proposing is changes that are part
of the way to implementing a noSQL/MongoDB backend to Django. That is
something that will require some additional discussion.
Some of this discussion has already happened. If you search the
archives, you will find many references to NoSQL support (Google
AppEngine and MongoDB are particular favorites). These discussions
have revealed that adding NoSQL support isn't just a matter of some
minor tweaks to AutoField handling; There are some major plumbing
changes that are required.
It's also worth noting that Alex Gaynor has been accepted as a Google
Summer of Code student, and his project is to start work on making the
modifications to the database backend that are required in order to
support NoSQL. He has specifically indicated that MongoDB will be the
backend he is initially targetting.
Regarding the specific proposed fixes: It's very hard to take changes
like this seriously when they aren't accompanied by tests. For
example, change (3) comments out code that exists for a specific
reason. If you run the test suite with that change applied, the
multiple_database tests have 13 failures and 2 errors. Tests aren't an
optional extra -- they're how you prove that you've actually thought
about the problem you're trying to solve.
Yours,
Russ Magee %-)