#23649: Oracle GIS testing -- fails to destroy old leftover test database after
unclean ending
-------------------------------------+-------------------------------------
Reporter: shaib | Owner: nobody
Type: | Status: new
Uncategorized | Version: master
Component: Database | Keywords: oracle testing
layer (models, ORM) | geodjango gis
Severity: Normal | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
If you run Django tests and they end without proper clean-up (e.g. the
test process is forcibly killed) then the next test run will try to
destroy the test-database before rebuilding it from scratch.
On Oracle GIS, this destroy-leftover-database process fails, because the
backend tries to drop the test tablespace (`DROP TABLESPACE TEST_DB
INCLUDING CONTENTS`), and for some reason the GIS artifacts make this
fail.
The workaround is to drop first the test user (`DROP USER TEST_USER
CASCADE`), but currently this needs to be done manually.
--
Ticket URL: <https://code.djangoproject.com/ticket/23649>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.288417f235de51b1d3b8622d96481c12%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
