Re: [Django] #31607: Subquery.__eq__() doesn't work properly for resolved subqueries.

2020-05-20 Thread Django
#31607: Subquery.__eq__() doesn't work properly for resolved subqueries.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (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 Mariusz Felisiak ):

 In [changeset:"52453b438a190f3f91fb0b19dee6184f91b176eb" 52453b4]:
 {{{
 #!CommitTicketReference repository=""
 revision="52453b438a190f3f91fb0b19dee6184f91b176eb"
 [3.0.x] Refs #31607 -- Added release notes for
 a125da6a7c79b1d4c55677d0bed6f9b1d7d77353.

 Backport of 8328811f048fed0dd22573224def8c65410c9f2e 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.31b2a6a339d6cd2d0ddf3c105acd8187%40djangoproject.com.


Re: [Django] #31607: Subquery.__eq__() doesn't work properly for resolved subqueries.

2020-05-20 Thread Django
#31607: Subquery.__eq__() doesn't work properly for resolved subqueries.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (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 Mariusz Felisiak ):

 In [changeset:"d5231719e0ec86dc6b71487e5461b34bac1c55f6" d5231719]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5231719e0ec86dc6b71487e5461b34bac1c55f6"
 [3.1.x] Refs #31607 -- Added release notes for
 a125da6a7c79b1d4c55677d0bed6f9b1d7d77353.

 Backport of 8328811f048fed0dd22573224def8c65410c9f2e 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ff50d046aa2c00a1f3593594bb6b1cc7%40djangoproject.com.


Re: [Django] #31607: Subquery.__eq__() doesn't work properly for resolved subqueries.

2020-05-20 Thread Django
#31607: Subquery.__eq__() doesn't work properly for resolved subqueries.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (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 GitHub ):

 In [changeset:"8328811f048fed0dd22573224def8c65410c9f2e" 8328811]:
 {{{
 #!CommitTicketReference repository=""
 revision="8328811f048fed0dd22573224def8c65410c9f2e"
 Refs #31607 -- Added release notes for
 a125da6a7c79b1d4c55677d0bed6f9b1d7d77353.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.29b9a35e435b17ac25a6df1523ee8523%40djangoproject.com.


Re: [Django] #31607: Subquery.__eq__() doesn't work properly for resolved subqueries.

2020-05-19 Thread Django
#31607: Subquery.__eq__() doesn't work properly for resolved subqueries.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (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 Mariusz Felisiak ):

 In [changeset:"0ba5aadb3377e49e995753944a7e5e55c3840bed" 0ba5aadb]:
 {{{
 #!CommitTicketReference repository=""
 revision="0ba5aadb3377e49e995753944a7e5e55c3840bed"
 [3.0.x] Fixed #31607 -- Fixed evaluated Subquery equality.

 Regression in 691def10a0197d83d2d108bd9043b0916d0f09b4.

 Backport of a125da6a7c79b1d4c55677d0bed6f9b1d7d77353 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.d485d815626977c417bf934ece38d386%40djangoproject.com.


Re: [Django] #31607: Subquery.__eq__() doesn't work properly for resolved subqueries.

2020-05-19 Thread Django
#31607: Subquery.__eq__() doesn't work properly for resolved subqueries.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (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 Mariusz Felisiak ):

 In [changeset:"937314dc05ee06eca91fcbb3ddf4380a60275b59" 937314d]:
 {{{
 #!CommitTicketReference repository=""
 revision="937314dc05ee06eca91fcbb3ddf4380a60275b59"
 [3.1.x] Fixed #31607 -- Fixed evaluated Subquery equality.

 Regression in 691def10a0197d83d2d108bd9043b0916d0f09b4.

 Backport of a125da6a7c79b1d4c55677d0bed6f9b1d7d77353 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.69acfbe47c81e955cf7eb6d250491490%40djangoproject.com.


Re: [Django] #31607: Subquery.__eq__() doesn't work properly for resolved subqueries.

2020-05-19 Thread Django
#31607: Subquery.__eq__() doesn't work properly for resolved subqueries.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (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 felixxm):

 * version:  3.1 => 3.0
 * stage:  Unreviewed => Accepted


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9065f26c7229e73d0362af4a12eb3c6f%40djangoproject.com.


Re: [Django] #31607: Subquery.__eq__() doesn't work properly for resolved subqueries.

2020-05-19 Thread Django
#31607: Subquery.__eq__() doesn't work properly for resolved subqueries.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"a125da6a7c79b1d4c55677d0bed6f9b1d7d77353" a125da6a]:
 {{{
 #!CommitTicketReference repository=""
 revision="a125da6a7c79b1d4c55677d0bed6f9b1d7d77353"
 Fixed #31607 -- Fixed evaluated Subquery equality.

 Regression in 691def10a0197d83d2d108bd9043b0916d0f09b4.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.51aebf462e8c18f6b4bde62460a3c061%40djangoproject.com.


Re: [Django] #31607: Subquery.__eq__() doesn't work properly for resolved subqueries.

2020-05-19 Thread Django
#31607: Subquery.__eq__() doesn't work properly for resolved subqueries.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/12936 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.4cd8b863d518e5802fd731d0da2afad9%40djangoproject.com.


Re: [Django] #31607: Subquery.__eq__() doesn't work properly for resolved subqueries.

2020-05-19 Thread Django
#31607: Subquery.__eq__() doesn't work properly for resolved subqueries.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * Attachment "test-31607.diff" added.

 Regression test.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.0c207e5c984d0c2fd26001e72696ba99%40djangoproject.com.