Hi all, I've now got the multiple-db-support branch fully merged up to date with trunk (as of rev 5559). As I've mentioned before it's in a mirrored repo, so I could commit all of the changesets incrementally back into the django svn repo (I've done 4 separate merges so far). I think that this approach has more value than one patch, as if I've screwed something up it might make it easier to catch without impacting on the other changes. On the other hand I understand the concerns raised earlier with letting anyone commit to django and I can supply a patch to one of the core devs instead if that is preferred :-).
There have been a few people who seem to be interested in moving forward with multi-db and i'd be really keen to get this stuff into svn one way or the other so others can get 'eyes on'. The tests are currently still a bit borked... They are basically locking up the django_session table in my test database (running postgres) around about the place where the output says "Request a page that modifies the session ... ok" i'm not sure what's going on and I don't think I know enough about it to find out in a reasonable space of time. Thanks Ben -- Regards, Ben Ford [EMAIL PROTECTED] +628111880346 --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
