#14415: Multiple aliases for one database: testing problems
-------------------------------------+-------------------------------------
Reporter: shai | Owner: boaz85
Type: Bug | Status: closed
Component: Testing framework | Version: master
Severity: Normal | Resolution: fixed
Keywords: multidb, multiple | Triage Stage: Accepted
databases, multiple aliases |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"5f23f904af387225b685c633014bddbec1cdd256" 5f23f90]:
{{{
#!CommitTicketReference repository=""
revision="5f23f904af387225b685c633014bddbec1cdd256"
Fixed #14415 -- Used the test database name in
BaseDatabaseCreation.test_db_signature().
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/14415#comment:27>
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/062.00a9560a0f77ebe1951b6e945e2f83d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
