Hey all,
Sorry for the slightly delayed update. This past week I worked on
completing the work on my m2m-refactor branch. Specifically I worked though
the review notes from my mentor, as well as ensuring all changes are
completely backwards compatibly. In addition I put together a backwards
compatibility plan for the last public (or semi-public) APIs that I need to
change for multi-db. For the remaining month or so I have the following
plans:
1. Update get_db_prep_* for multi-db, adding a connection paramtere while
retaining backwards compatibility.
2. Refactor the way we create the Query class from BaseQuery. Specifically
this needs to be done in a way that let's us switch from a regular Query to
an Oracle query safely (or vice versa, or a custom query, or whatever).
3. Handle
Model.objects.using('db1').filter(id__in=Model.objects.using('db2'))
correctly. I think we already have the machinery in place for this to work
and it's just a matter of putting the pieces together, but if not I'll get
it to happen.
4. Make sure this m2m work gets in.
Plus fixing any bugs as they come. Depending on how long this stuff takes I
may add fixing up contrib.gis to it. I've changed lots of internal APIs and
that will, without a doubt break GIS. Time permitting I'll try to fix that,
else it'll just happen post-GSOC.
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 [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
-~----------~----~----~----~------~----~------~--~---
