On Fri, Nov 20, 2009 at 1:14 AM, Alex Gaynor <[email protected]> wrote:
> Hey all, > > Russ and I have been working on getting the multi-db work ready for > merge (final stretch here hopefully!), and I just ported the Oracle > backend to the slightly updated backend arcitecture so it could use > some testers. If you've got an Oracle setup and can run some tests > that would be great. You can grab the code here: > > http://github.com/alex/django/tree/multiple-db > > Make sure you use the multiple-db branch. I understand running the > tests under Oracle can be a bit slow, so perhaps start by just running > the "queries" tests, if they fail please reply with the complete > tracebacks and such here, otherwise if you have the time a shot at > running the full test suite would be great. > > The queries test ran OK once I removed: from django.db.backends.oracle import query from django/db/backends/oracle/base.py I guessed based on the fact that django/db/backends/oracle/query.py was removed in the last commit that the import was leftover from a restructuring. I am not sure but it looks like there may also be some other dead stuff referencing this query module (the query_class method in DatabaseOperations?), but I did not touch that, just removed that one import. I've got the full suite running now, but that will take a while. So far I am testing with just Oracle backend specified. The last time I tested this branch I also had a test config that specified multiple dbs -- a default and an extra one. Not sure if you wanted to test that at this point so I started with the simpler one. Karen -- 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=.
