#14443: Oracle backend returns wrong test database name
---------------------------------------------------+------------------------
Reporter: gruszczy | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by ramiro):
* stage: Unreviewed => Accepted
Comment:
In the days when the 1.1 release was near there was some work in this area
of the code. Please see changesets r10547 and r10608 and its associated
ticket: #10716 (also, r8330 from the 1.0 development cycle). Note how some
attempts to rationalize things that arose from simple code inspection had
to be undone
IMHO, certainly it would be helpful if somebody with a) access to a
working Oracle setup, b) Oracle experience and c) time do dedicate to the
task could make and test a holistic review and cleanup of the code. I can
submit the resulting patch for review by the Oracle experts in the core
development team and commit it if all goes ok.
a) and b) are critical because AFAIK e.g. the Django test suite is running
now under Oracle in these conditions and we don be the ones that break it,
aren't we :)
--
Ticket URL: <http://code.djangoproject.com/ticket/14443#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
