[Django] #31988: Annotate Case(When()) duplicate objects

[Django]

#31988: Annotate Case(When()) duplicate objects
-+-
   Reporter:  Vladimir   |  Owner:  nobody
  Kuznetsov  |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.1
  layer (models, ORM)|   Keywords:  duplicate annotate
   Severity:  Normal |  case when
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Hey! I have some simple models here:
 {{{
 class Token(models.Model):  # User in my project.
 token = models.UUIDField(db_index=True)
 ...


 class Question(models.Model):
 is_answered = models.BooleanField(default=False)
 ...


 class Like(models.Model):  # Not created for all users automatically if
 new question created.
 question = models.ForeignKey(Question, on_delete=models.CASCADE,
 related_name='likes')
 token = models.ForeignKey(Token, on_delete=models.CASCADE)
 like_value = models.IntegerField(default=0)

 }}}

 And I wanna do filter with annotate (get all unanswered questions and show
 user's like value):
 {{{
 x_id = self.context.get('request').META.get('HTTP_X_CLIENT_TOKEN')  # just
 UUID

 questions = Question.objects.filter(
 is_answered=False
 ).annotate(
 my_like=Case(
 When(Q(likes__token__token=x_id) & Q(likes__like_value=1),
 then=1),
 When(Q(likes__token__token=x_id) & Q(likes__like_value=-1),
 then=-1),
 default=Value(0),
 output_field=IntegerField()
 )
 )

 }}}

 The problem clearly shown here:
 {{{
 >>> print(Question.objects.filter(is_answered=False).count())
 4
 >>> print(questions.count())
 7

 }}}

 Duplicate happened if other user(s) liked the same question(s) which
 current user liked. If I call `questions.query` I'll get `LEFT OUTER JOIN`
 in SQL request.
 It can be fixed in this way:
 {{{
 user_liked_questions = Question.objects.filter(likes__like_value=1,
 likes__token__token=x_id)
 user_disliked_questions = Question.objects.filter(likes__like_value=-1,
 likes__token__token=x_id)

 questions = Question.objects.filter(
 is_answered=False
 ).annotate(
 my_like=Case(
 When(id__in=user_liked_questions, then=1),
 When(id__in=user_disliked_questions, then=-1),
 default=Value(0),
 output_field=IntegerField()
 )
 )

 }}}

 Insofar as query is lazy this filter converting in one SQL request, not
 three. But it still not really comfortable and not understandable why
 first version didn't work in the same way as second one.

-- 
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/050.ea3d6fe7adf866b2c9b0f8706d5a531e%40djangoproject.com.

Re: [Django] #31962: Raise a more appriopriate exception when session cannot be updated.

[Django]

#31962: Raise a more appriopriate exception when session cannot be updated.
-+-
 Reporter:  Alex Vandiver|Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.sessions |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * stage:  Accepted => Ready for checkin


-- 
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/064.2ffe62afb41b79297cad9123777c863d%40djangoproject.com.

Re: [Django] #31987: Cast() crashes with DurationField on MySQL.

[Django]

#31987: Cast() crashes with DurationField on MySQL.
-+-
 Reporter:  Petr Čermák  |Owner:  Petr
 |  Čermák
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  mysql| Triage Stage:  Ready for
 |  checkin
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:"fc1446073ed9636047c48796cc20772ab60e12b0" fc144607]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc1446073ed9636047c48796cc20772ab60e12b0"
 Fixed #31987 -- Fixed Cast() with DurationField on MySQL.
 }}}

-- 
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/064.105a69d35aa5633b668203cc50bf7fb8%40djangoproject.com.

Re: [Django] #31973: TypeError loading data in JSONField if DB has native JSON support

[Django]

#31973: TypeError loading data in JSONField if DB has native JSON support
-+-
 Reporter:  Adam Alton   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by felixxm):

 > I’m not using any custom JSONField stuff, only the built-ins. It does
 appear that because only the json.JSONDecodeError is being caught as an
 exception, its missing the case where—because of the DBs built-in JSON
 support—the data has already been converted.

 The data shouldn't be converted because Django uses a
 
[https://github.com/django/django/blob/5ea1621c724e765c9a642a1b3b6e83419fda920b/django/db/backends/postgresql/base.py#L203-L206
 custom stub converter]. Please provide a sample project that reproduces
 this issue.

-- 
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/067.26817ced2967671b2901236d307550fa%40djangoproject.com.

Re: [Django] #31987: Cast() crashes with DurationField on MySQL. (was: Cast() crashes with DurationField on MySQL and Oracle.)

[Django]

#31987: Cast() crashes with DurationField on MySQL.
-+-
 Reporter:  Petr Čermák  |Owner:  Petr
 |  Čermák
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * stage:  Accepted => Ready for checkin


-- 
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/064.adff16b521568a3076e243d2c50a3714%40djangoproject.com.

Re: [Django] #31987: Cast() crashes with DurationField on MySQL and Oracle.

[Django]

#31987: Cast() crashes with DurationField on MySQL and Oracle.
-+-
 Reporter:  Petr Čermák  |Owner:  Petr
 |  Čermák
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


Comment:

 Submitted test looks great, suggested a way to reduce without involving
 multiple objects and aggregation.

-- 
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/064.be6209701991948adb7d1c9267193242%40djangoproject.com.

Re: [Django] #31636: BooleanFieldListFilter doesn't respect field choices.

[Django]

#31636: BooleanFieldListFilter doesn't respect field choices.
---+-
 Reporter:  Maxence G  |Owner:  Manav Agarwal
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by Manav Agarwal):

 * owner:  Ninad Kulkrni => Manav Agarwal


-- 
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/068.5b81e9ad329b638a3d5ab3b462c23b37%40djangoproject.com.

Re: [Django] #31987: Cast() crashes with DurationField on MySQL and Oracle. (was: Cast() crashes with DurationField on MySQL.)

[Django]

#31987: Cast() crashes with DurationField on MySQL and Oracle.
-+-
 Reporter:  Petr Čermák  |Owner:  Petr
 |  Čermák
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

-- 
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/064.8ad999eb01fee63bbf7a902db66b788e%40djangoproject.com.

Re: [Django] #31987: Cast() crashes with DurationField on MySQL. (was: Cast data type for DurationField is mising for MySQL)

[Django]

#31987: Cast() crashes with DurationField on MySQL.
-+-
 Reporter:  Petr Čermák  |Owner:  Petr
 |  Čermák
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  nobody => Petr Čermák
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/13398 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/064.7e2160275a20a58575b157ccb94a5723%40djangoproject.com.

Re: [Django] #31777: Custom collations

[Django]

#31777: Custom collations
-+-
 Reporter:  Tom Carrick  |Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   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 Tom Carrick):

 * needs_better_patch:  1 => 0


-- 
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.ca51872d4e58df4bb8f4f09942d65d53%40djangoproject.com.

Re: [Django] #31962: Raise a more appriopriate exception when session cannot be updated.

[Django]

#31962: Raise a more appriopriate exception when session cannot be updated.
-+-
 Reporter:  Alex Vandiver|Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.sessions |  Version:  master
 Severity:  Normal   |   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 Hasan Ramezani):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


-- 
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/064.b4a7f166754b68d84d7e4fadfc34d59d%40djangoproject.com.

Re: [Django] #31987: Cast data type for DurationField is mising for MySQL

[Django]

#31987: Cast data type for DurationField is mising for MySQL
-+-
 Reporter:  Petr Čermák  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 Haven't reproduced but you'll need a regression test to demonstrate the
 issue this addresses.

-- 
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/064.77dbced715b9cd680ca3d849cf263469%40djangoproject.com.

[Django] #31987: Cast data type for DurationField is mising for MySQL

[Django]

#31987: Cast data type for DurationField is mising for MySQL
-+-
   Reporter:  me2d09 |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.1
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  mysql
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 It is not possible to use:
 {{{
 django.db.models.functions.Cast(x, output_field=DurationField())
 }}}
 because it generated `CAST(xxx AS bigint)` which is not valid MySQL
 syntax.

-- 
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/049.fd516fb57e9e628909ac9418a0f305e0%40djangoproject.com.

Re: [Django] #27257: Use the ->> operator when filtering builtin text lookups on JSONField keys

[Django]

#27257: Use the ->> operator when filtering builtin text lookups on JSONField 
keys
-+-
 Reporter:  Nick Stefan  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by felixxm):

 Alym, please don't edit old comments. If you want to report any regression
 in Django 3+, create a new ticket.

-- 
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/068.8be0d09db2a187da99717e15787af28d%40djangoproject.com.

Re: [Django] #27257: Use the ->> operator when filtering builtin text lookups on JSONField keys

[Django]

#27257: Use the ->> operator when filtering builtin text lookups on JSONField 
keys
-+-
 Reporter:  Nick Stefan  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alym):

 Problem repeats in django 3

-- 
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/068.97294668eb9d8b06f6a9a72c43f31c9b%40djangoproject.com.

Re: [Django] #24082: Unique=True on TextField or CharField should not create an index

[Django]

#24082: Unique=True on TextField or CharField should not create an index
-+-
 Reporter:  djbug|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Peter Thomassen):

 * cc: Peter Thomassen (added)


-- 
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/063.84889b3c7ab0323be86a859c733bf9c0%40djangoproject.com.

Re: [Django] #31986: Django Admin filter sidebar does not scroll.

[Django]

#31986: Django Admin filter sidebar does not scroll.
-+
 Reporter:  haki |Owner:  007
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  3.1
 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 felixxm):

 * owner:  nobody => 007
 * status:  new => assigned
 * has_patch:  0 => 1


-- 
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/062.69f1481df00f15690be90308ac3c9362%40djangoproject.com.

Re: [Django] #31986: Django Admin filter sidebar does not scroll.

[Django]

#31986: Django Admin filter sidebar does not scroll.
-+
 Reporter:  haki |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  3.1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by 007):

 At first, I solved the problem with absolute positioning. But it doesn't
 look very beautiful. So we use `overflow:hidden` to trigger
 [https://developer.mozilla.org/en-
 US/docs/Web/Guide/CSS/Block_formatting_context  BFC] solve the problem.
 But unfortunately it led to other problems. So go back to the absolute
 positioning solution.

 [https://github.com/django/django/pull/13397 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/062.63d120b6f735709f53613b9d2c5a6c92%40djangoproject.com.

Re: [Django] #31986: Django Admin filter sidebar does not scroll. (was: Django Admin filter sidebar does not scroll)

[Django]

#31986: Django Admin filter sidebar does not scroll.
-+
 Reporter:  haki |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  3.1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by felixxm):

 * cc: 007, Tom Carrick (added)
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for this report.

 Regression in 2bc38bc7cae002f949157d95e3f0c19ea6b8ca5c (Django 3.1.1).

 Reproduced at 5ea1621c724e765c9a642a1b3b6e83419fda920b.

-- 
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/062.83f518d08bb0d6c34b9aaf2c95cc3edc%40djangoproject.com.

Re: [Django] #31777: Custom collations

[Django]

#31777: Custom collations
-+-
 Reporter:  Tom Carrick  |Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  0 => 1


-- 
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.003fe04dda177911df75a8fd21355df6%40djangoproject.com.

[Django] #31986: Django Admin filter sidebar does not scroll

[Django]

#31986: Django Admin filter sidebar does not scroll
-+
   Reporter:  haki   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  3.1
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Starting at Django 3.1, when the Django admin filter sidebar is very long,
 it does not scroll.

 For example:

 https://imgur.com/jwnFmYo

 Notice how the filter overflows the screen, making the filters on the
 bottom unreachable.

 I've only witnessed this behavior starting at Django 3.1, when the layout
 of the screen changes for the sidebar.

-- 
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/047.91e316e938b31697f999652f02636945%40djangoproject.com.

Re: [Django] #28936: simplify_regex should remove redundant escape sequences outside groups

[Django]

#28936: simplify_regex should remove redundant escape sequences outside groups
-+-
 Reporter:  Cristi Vîjdea|Owner:  (none)
 Type:  Bug  |   Status:  closed
Component:  contrib.admindocs|  Version:  2.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  simplify_regex path  | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Carlton Gibson):

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


Comment:

 Thanks for the patch Oliver.

 > ... I am not sure it really needs to be fixed.

 I think this is right.

 As with the DRF issue, calling `str()` on `path.pattern` before passing to
 `simplify_regex()` is the correct usage, and
 
[https://github.com/django/django/blob/5ea1621c724e765c9a642a1b3b6e83419fda920b/django/contrib/admindocs/views.py#L389
 it is what `admindocs` does].

 Here using [https://github.com/encode/django-rest-
 framework/issues/5675#issue-282663045 the original example from the DRF
 issue]:

 {{{
 >>> from django.urls import path
 >>> from django.contrib.admindocs.views import simplify_regex
 >>> p = path('^api/token-auth/', lambda: None)  # Not sure about the `^`,
 but either way…
 >>> p.pattern
 
 >>> p.pattern.regex.pattern
 '^\\^api/token\\-auth/$'
 >>> simplify_regex(p.pattern.regex.pattern)  # Wrong usage.
 '/\\api/token\\-auth/'
 >>> str(p.pattern)
 '^api/token-auth/'
 >>> simplify_regex(str(p.pattern))  # Correct usage.
 '/api/token-auth/'
 }}}

-- 
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/066.7b3a9a0f5265f2c5ce4d46ffbfd160cb%40djangoproject.com.

Re: [Django] #31766: Avoid unneccessary computation in GDALRaster.transform().

[Django]

#31766: Avoid unneccessary computation in GDALRaster.transform().
-+-
 Reporter:  Riccardo |Owner:  Barton Ip
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  GDALRaster; GIS  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * easy:  1 => 0
 * stage:  Accepted => Ready for checkin


-- 
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.75054e5ef8baa6f90ad82a6bd910d636%40djangoproject.com.