#22683: Schema tests and .extra queryset method
-------------------------------------+-------------------------------------
Reporter: maxi | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version:
Component: Migrations | 1.7-beta-2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by andrewgodwin):
* status: new => closed
* resolution: => wontfix
Comment:
Unfortunately, we can't use the model there - it doesn't have the added
column (we can't mutate the models in the schema tests as they're used for
multiple tests - the test just runs add_field on it, there's nothing in
there that actually adds it to the model and runs contribute_to_class).
Given the fragility of moving this to add itself and then undo the damage
shortly after, and the fact that this test is passing just fine on all
backends AFAIK (unquoted names are valid SQL, and I'm not aware of any DBs
with 'thing' as a keyword), I'm going to close this as WONTFIX. Someone
should reopen if a database is discovered where this breaks.
--
Ticket URL: <https://code.djangoproject.com/ticket/22683#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/062.c74cdbc7f86e6636a2a3130cb4d24052%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
