Re: [Django] #28197: PostgreSQL introspection's get_constraints() retrieves index fields in arbitrary order

[Django]

#28197: PostgreSQL introspection's get_constraints() retrieves index fields in
arbitrary order
-+-
 Reporter:  Mactory  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"566726ff964b004f2a6adecc1e51197bc34d78d2" 566726ff]:
 {{{
 #!CommitTicketReference repository=""
 revision="566726ff964b004f2a6adecc1e51197bc34d78d2"
 [1.11.x] Fixed #28197 -- Fixed introspection of index field ordering on
 PostgreSQL.

 Backport of 3a5299c19cd5a38f7fa0f45ed2df7b10f0c9cf5d from master
 }}}

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.2296ec67ff104bcd62b5a3474567324a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28197: PostgreSQL introspection's get_constraints() retrieves index fields in arbitrary order

[Django]

#28197: PostgreSQL introspection's get_constraints() retrieves index fields in
arbitrary order
-+-
 Reporter:  Mactory  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 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 Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"3a5299c19cd5a38f7fa0f45ed2df7b10f0c9cf5d" 3a5299c]:
 {{{
 #!CommitTicketReference repository=""
 revision="3a5299c19cd5a38f7fa0f45ed2df7b10f0c9cf5d"
 Fixed #28197 -- Fixed introspection of index field ordering on PostgreSQL.
 }}}

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1e550c4ec0c83fc22ee5a4dd0e0fc5c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28197: PostgreSQL introspection's get_constraints() retrieves index fields in arbitrary order

[Django]

#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: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
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.

Re: [Django] #28197: PostgreSQL introspection's get_constraints() retrieves index fields in arbitrary order

[Django]

#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:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 From the PostgreSQL docs:
   The aggregate functions array_agg, json_agg, json_object_agg,
 string_agg, and xmlagg, as well as similar user-defined aggregate
 functions, produce meaningfully different result values depending on the
 order of the input values. This ordering is unspecified by default, but
 can be controlled by writing an ORDER BY clause within the aggregate call,
 as shown in Section 4.2.7. Alternatively, supplying the input values from
 a sorted subquery will usually work.`

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.139ce14502197739de11727de301f4b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28197: PostgreSQL introspection's get_constraints() retrieves index fields in arbitrary order (was: db.backends.postgresql.introspection.get_constraints retrieves index fields in arbitra

[Django]

#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:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1
 * severity:  Normal => Release blocker
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Looks like a regression in f842d1011c1195aa26071a6ab6f96e0b8d907343. Can
 you add a regression test to the PR?

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.19982566d26d70af50fe812b5efb84e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.