On Jan 8, 1:10 pm, Waldemar Kornewald <[email protected]> wrote: > Hi, > our non-relational port has come to the point where we need to > back-port the SQL layer to the query backend API (i.e., the new > query_class()). We could need some help from Django developers who > know the ORM internals really well. You can find a little introduction > to the code > here:http://bitbucket.org/wkornewald/django-nonrel-multidb/wiki/Home > > It would be great if one core developer could join the project and > actually work on the code. Here's the discussion > group:http://groups.google.com/group/django-non-relational > > The difficulty is that we need to convert QuerySet's intermediate > representation (QueryData) to the sql.Query representation. We're not > sure if QueryData in its current implementation has the right format > and someone who knows sql.Query better than we do could be of great > help, especially with the conversion process. Our goal is to get > non-relational backend support into Django 1.3 (which is definitely > possible, so please don't vote -1 next time if this is your only > concern). > > I understand if you're currently busy with finishing 1.2, but if > you're interested in helping when will you have time? >
Is nobody out there with a little bit of time/interest in helping? It would be really nice and would speed up the development of supporting non-relational databases for Django. Bye, Thomas Wanschik > Bye, > Waldemar Kornewald > > --http://twitter.com/wkornewaldhttp://bitbucket.org/wkornewald/http://allbuttonspressed.blogspot.com/
-- 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.
