#17786: Exception when running the tests under Oracle
-----------------------------------+--------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.4-beta-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by akaariai):
* cc: anssi.kaariainen@… (added)
Comment:
This is almost definitely connected to r17411. That patch caused the drop
database code to use a new connection for dropping the database. The
Oracle code expects the dropping to be done by the same connection.
The right fix seems to be returning the "remember" dictionary from the
_create_test_db(), and then again passing it to _destroy_test_db(). Or,
you could get hacky and have a class level remember variable in the
creation code, mapping connection alias to remember dictionary of that
alias. It should work but as said, it is a little ugly... Even uglier is
just assigning the creation from the old connection to the new temporary
connection.
--
Ticket URL: <https://code.djangoproject.com/ticket/17786#comment:1>
Django <https://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-updates@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.
