#25357: setup_databases doesn't deduplicate databases correctly on Oracle
---------------------------------------------+------------------------
               Reporter:  aaugustin          |          Owner:  nobody
                   Type:  Bug                |         Status:  new
              Component:  Testing framework  |        Version:  master
               Severity:  Normal             |       Keywords:
           Triage Stage:  Unreviewed         |      Has patch:  0
    Needs documentation:  0                  |    Needs tests:  0
Patch needs improvement:  0                  |  Easy pickings:  0
                  UI/UX:  0                  |
---------------------------------------------+------------------------
 The short version is that, when `setup_databases` detects that two
 databases are identical, it does `connection.settings_dict['NAME'] = ...`
 instead of calling `connection.creation.set_as_test_mirror()`.

 I'm going to attach a project that allows reproducing the issue.
 (Unfortunately, we don't have a convenient way to test the test runner's
 database creation features.)

 If you set `DATABASES = DATABASES_POSTGRES` in the settings, the test
 passes.

 If you set `DATABASES = DATABASES_ORACLE` in the settings, the test fails
 with `myapp.models.DoesNotExist: MyModel matching query does not exist.`.

--
Ticket URL: <https://code.djangoproject.com/ticket/25357>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.d40d439578935fa1da8c042b1264a749%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to