Here is the current status of Oracle support: - Some of the backend files are already in subversion trunk, but not enough to make it functional. Don't bother testing (or patching) Oracle support in the trunk--the branch is where the action is. - Some Colorado developers, along with Jacob Kaplan-Moss, made a valiant attempt to finish Oracle support at a sprint about two months ago. That's now the boulder-oracle-sprint branch. - To run the unit test suite, do "python tests/runtests.py --settings=myproject.settings" from the root of the boulder-oracle-sprint branch. Make sure myproject.settings is a python module in your PYTHONPATH that is configured to connect to an Oracle database. The Oracle user you specify must have DBA-type privileges, since the tests create and destroy tables, indexes, triggers, and tablespaces. (Also don't include a CACHE_BACKEND in settings.py, or the cache-related tests will fail.) - Currently, only two tests fail against Oracle. We could really use help fixing those! - A bigger problem is the potential column name collision owing to the fact that our paging query uses a "SELECT *" construct around the main SQL. (Don't scold me; we're trying to fix it.) - Another issue is that Date and DateTime fields show up as Boolean values in the Admin. - I merged changes from the django trunk into the boulder-oracle-sprint branch today, and will continue to do so on a weekly basis until Oracle support is in the trunk.
Questions about Django development in general are answered here: http://www.djangoproject.com/documentation/contributing/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
