m2m_through test hasn't a really predictable output
|Reported by:||ramiro||Owned by:||nobody|
|Severity:||Keywords:||m2m_through db backend output modeltests|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
One of the tests for this new functionality:
runs successfully with all (some?) the builtin DB backends, but from what can be seen in the model definitions and the data handling made in the tests leading to that specific test, there isn't an unique 'correct' output order.
This is showing a a failure when running the test suite against another external DB backend.
The attached patch solves this adding another item to the membership.meta.ordering tuple.