#28197: PostgreSQL introspection's get_constraints() retrieves index fields in
arbitrary order
-------------------------------------+-------------------------------------
Reporter: Mactory | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mactory):
* needs_tests: 1 => 0
Comment:
I have extended the existing tests to also test a 4 field index. The test
fails on my machine without the patch and passes with the patch.
Since the ordering of the fields was, as far as I could see it, arbitrary,
it could happen though, that the problem exists but is not detected by the
test. This can be if the ordering just happens to be correct. I don't see
any possibility though to catch randomly correct orderings in a test. If
you know any techniques to do so, please feel free to extend the tests
further.
[https://github.com/django/django/pull/8495 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/28197#comment:4>
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/065.4f71129c1584dea13b78fce932045e6a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
