On 6/8/07, Ben Ford <[EMAIL PROTECTED]> wrote: > Hi, > The branch is now up to date as of 5371 (from 4188, yes _stale_ is one word > you could use) in my local svk repo. Some of the tests are failing, (but > they're also failing at the same point when I run the tests in trunk too, so > I'm not quite sure what's going on!!).
Which tests? Are you running MySQL? There are some known test failures due to problems in the way MySQL handles row-level integrity. > As for bug fixes I have my eye on > 3642 and 3885. Both of these refer to ForeignKeys breaking down at the point > where the relation crosses from one db to another. I think this is a worthy > feature as i guess the whole point of integrating other db's into your > django app is to interace with existing objects. Agreed. > I'm thinking of another > kind of Field (perhaps OtherDBForeignKey) and Descriptor objects to solve > this... Hrm... my gut reaction is that the model description shouldn't know it is separated across databases; this is a deployment issue, so it wouldn't be good to hard code deployment into the model. > Also off the top of my head i would imagine django.db.models.query > will need some TLC to make it work too!! The queryset is (hopefully) about to undergo a bit of a refactor; so: 1) Don't base too much of your changes on massive reworkings of query.py 2) If you come across any refactorings that would be useful - especially in relation to writing custom fields, etc - make sure you make them known. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
