#15068: initial_data fixtures using natural keys fail in tests with multiple
databases
----------------------------------------+-----------------------------------
Reporter: dcramer | Owner: nobody
Status: closed | Milestone:
Component: Testing framework | Version: 1.2
Resolution: invalid | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => invalid
* component: Uncategorized => Testing framework
* stage: Unreviewed => Accepted
Comment:
I'm having difficulty in seeing how this situation would arise. Fixtures
can't cross databases, and they are saved raw on the database they're
being loaded onto. All test databases are created before the first test is
created. I can't see how a test fixture -- which is loaded after all the
databases have been configured -- could cause "table does not exist" or
"database does not exist" errors.
Closing invalid; As with #15063, feel free to reopen if you can provide a
comprehensive report that describes (or better yet, demonstrates) exactly
how this would occur.
--
Ticket URL: <http://code.djangoproject.com/ticket/15068#comment:2>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
