Hey all,

This week I made the final major API changes, updating the
get_db_prep_* methods to recieve connection, and work in a backwards
compatible method.  I also fixed the bug with using
__in=queryset.using('other_db'), right now it raises an exception, but
in the future I'll update it to just do 2 queries and substitute the
results of the first into the second.  This week my big goal is to
refactor the whole Query/BaseQuery issue, and change the way custom
backends are handled.  I *think* this should be relatively
straightforward, but it may be a little complex, so I'll probably ping
the mailing list as soon as possible to see if anyone with a backend
using a custom query class can test it out.  Next weekend I'll be
giving a talk at PyOhio and holding a Django sprint, so I may or may
not have a lot of time that weekend.  Also, I've heard from at least
one person that they've been able to use the branch successfully, so
that's good news :)

Alex

-- 
"I disapprove of what you say, but I will defend to the death your
right to say it." -- Voltaire
"The people's good is the highest law." -- Cicero
"Code can always be simpler than you think, but never as simple as you
want" -- Me

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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
-~----------~----~----~----~------~----~------~--~---

Reply via email to