#27571: Conditionally add TEST_DATABASE_PREFIX to db name
-------------------------------------+-------------------------------------
Reporter: Alex Alvarez | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
TEST_DATABASE_PREFIX | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Alex Alvarez):
Isn't this backwards-incompatible? yeah it is.
As I mentioned the behavior is documented, I was just curious if anyone
else thought like me and found it annoying that said database name changes
even when you follow the naming convention.
For me, I'm operating in mixed environment where not all db connections
are instantiated from django and it caused a lot of headache before
realizing the db name was being renamed just because I changed from sql-
lite to postgres
--
Ticket URL: <https://code.djangoproject.com/ticket/27571#comment:2>
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/075.a2485f6614e33f63a7218dafecbc25c0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.