Re: [Django] #31289: system checks: admin.E002 could provide a hint but doesn't

[Django]

#31289: system checks: admin.E002 could provide a hint but doesn't
-+-
 Reporter:  Keryn Knight |Owner:  Sanskar
 Type:   |  Jaiswal
  Cleanup/optimization   |   Status:  assigned
Component:  Core (System |  Version:  3.0
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  1 => 0
 * has_patch:  0 => 1
 * stage:  Accepted => Ready for checkin


Comment:

 [https://github.com/django/django/pull/12484 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/067.5c6514f35b0e4e9d9e980b5ea187b8ab%40djangoproject.com.

Re: [Django] #31211: Add SearchConfig expression.

[Django]

#31211: Add SearchConfig expression.
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 Type:   |  Ljungberg
  Cleanup/optimization   |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   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:"d0f1c03331718f1b146cf0fd6ffefa19538eebe4" d0f1c033]:
 {{{
 #!CommitTicketReference repository=""
 revision="d0f1c03331718f1b146cf0fd6ffefa19538eebe4"
 Refs #31211 -- Prevented SearchConfig nesting in SearchVector and
 SearchQuery init.

 Passing a SearchConfig instance directly to SearchVector and
 SearchQuery would result in nested SearchConfig instance.
 }}}

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

Re: [Django] #3254: full text search support for postgres, oracle and mssql

[Django]

#3254: full text search support for postgres, oracle and mssql
-+-
 Reporter:  Ronny Pfannschmidt   |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle fulltext  | Triage Stage:  Accepted
  search postgresql postgres mysql   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"3d62ddb02695cfafc847951b45e6e1ec5dc0b149" 3d62ddb0]:
 {{{
 #!CommitTicketReference repository=""
 revision="3d62ddb02695cfafc847951b45e6e1ec5dc0b149"
 Refs #3254 -- Removed unnecessary truth check in
 SearchVectorExact.as_sql().

 Direct usage of the @@ operator is perfectly allowed.
 }}}

-- 
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/076.8a586e2157ef4fda10f6c2beae25a3b5%40djangoproject.com.

Re: [Django] #31301: bulk_create with ForeignKey fields with mixed filled/None values fails

[Django]

#31301: bulk_create with ForeignKey fields with mixed filled/None values fails
-+-
 Reporter:  Hans Aarne Liblik|Owner:  Hardik
 |  Patel
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle sql   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Hans Aarne Liblik):

 Any progress on this? If not, I can take over.

-- 
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/073.f327521f46fab51413a8cc8aab4fc97b%40djangoproject.com.

Re: [Django] #29789: Support nested relations in FilteredRelation's condition

[Django]

#29789: Support nested relations in FilteredRelation's condition
-+-
 Reporter:  Thomas Riccardi  |Owner:  Noumbissi
 |  Valere Gille Geovan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  FilteredRelation | Triage Stage:  Accepted
  nested relations   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Matt Ferrante):

 * 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/073.356f871b45e7030f01c1ef50af975ca4%40djangoproject.com.

Re: [Django] #31304: PostgreSQL full-text search employs coalesce function for non-null single-column searches with SearchVector

[Django]

#31304: PostgreSQL full-text search employs coalesce function for non-null 
single-
column searches with SearchVector
-+-
 Reporter:  Paul Boddie  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  PostgreSQL text  | Triage Stage:  Accepted
  search FTS coalesce SearchVector   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * cc: Simon Charette (added)


Comment:

 > I wouldn't expect to_tsvector to treat an empty string and null in the
 same way - this being SQL after all - but the aim would be to avoid
 coalesce where null could never occur. This then becomes an issue of
 knowing when this might be guaranteed.

 Right the main issue here is that `SearchVector` (just like `Concat` for
 example) has been coalescing nulls to empty strings forever so we can't
 just change it now without breaking backward compatibility.

 > I'm still getting familiar with the ORM, but I imagine that there could
 easily be cases where column values are null even if the table columns are
 declared not null. For instance, any query involving an outer join could
 produce null values for a "not null" column. In such cases, the
 characteristics of the output column would need to be defined by
 identifying its role in the query, pretty much as you say.

 Right comment:6 provides another example of that. The `JOIN` resolution
 logic knows about these things but it's not surfaced at the `Expression`
 introspection level right now so we can't even start deprecating the
 current behaviour if we wanted to. I plan on working on patch that exposes
 an `Expression.nullable` property that gets assigned on field reference
 resolution but that's not an easy thing to get right as you might suspect.

 > I am inclined to think that making my own lookup would be the safest
 thing to do for now, with the lookups provided also considering the issue
 of transferring the configuration.

 I tend to agree, are you still interested in submitting a PR that does a
 `config` assignment in `SearchLookup.process_lhs`?

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

Re: [Django] #31295: required ModelChoiceField makes duplicate (cursor) queries to the database

[Django]

#31295: required ModelChoiceField makes duplicate (cursor) queries to the 
database
-+--
 Reporter:  Aurélien Pardon  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:  Model| Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Aurélien Pardon):

 * status:  closed => new
 * type:  Cleanup/optimization => Bug
 * resolution:  wontfix =>


Comment:

 Hi Carlton and thanks for your answer but, all due respect, I think you
 overlooked this bug.

 First, this simple example on an empty project/database that I just tested
 (Python 3.8.1, Django 2.2.10):
 {{{#!python
 class MyModel(models.Model):
 my_field = models.CharField(max_length=1)

 class MyForm(forms.Form):
 my_form_field = forms.ModelChoiceField(MyModel.objects.all(), ,
 empty_label=None)

 my_form = MyForm()
 type(my_form.widget.choices)
 # >>> return 

 my_form.as_ul()
 len(connecton.queries)
 # >>> return 2 (and it's two times "SELECT * from my_app.my_model")
 }}}

 Here is what I understand:
 1) The code you sent, where {{{ChoiceWidget.choices}}} is evaluated and
 saved into a {{{list}}} is executed at the initialization of the widget
 (which is executed at the initialization of the field at the declaration
 of the form).
 2) But! a {{{ModelChoiceField}}} override {{{self.choices}}}
 
[https://github.com/django/django/blob/271fdab8b78af558238df51c64b4d1c8dd0792bb/django/forms/models.py#L1225-L1227
 here] (it makes perfect sense: the choices have to be evaluated everytime
 the form is instanciated).
 3) As the choices are bundled in a
 {{{ModelChoiceIterator}}}/{{{.iterator()}}}, when rendering the form,
 there is a test about the {{{required}}} attribute that try to
 
[https://github.com/django/django/blob/ffcf1a8ebfbdc8e3afac84aed88d6ed29a57c72b/django/forms/widgets.py#L699
 fetch the first value of the queryset]:
 {{{#!python
 class Select(ChoiceWidget):
 """[...]"""
 def use_required_attribute(self, initial):
 """[...]"""
 first_choice = next(iter(self.choices), None)
 }}}
 4) {{{ModelChoiceIterator.__iter__}}}
 
[https://github.com/django/django/blob/ffcf1a8ebfbdc8e3afac84aed88d6ed29a57c72b/django/forms/models.py#L1148-L1156
 is called]. If {{{empty_label}}} is {{{not None}}}, everything is fine, as
 the {{{next()}}} grabs the empty label, without additional request to the
 database. But if {{{empty_label}}} is {{{None}}} (and if there is no
 prefetch to the queryset), an additional request is made (code is changed
 lightly to illustrate the bug):
 {{{#!python
 def __iter__(self):
 if self.field.empty_label is not None:
 yield ("", self.field.empty_label)
 for obj in self.queryset.iterator():
 yield self.choice(obj)
 }}}

 Now that I have made some tests on an empty project/database, I'm
 confident enough to state that it's a **bug** because there is a useless
 and additional request to the DB.

 ''Thanks for all the work you put into the projects in and around Django.
 I hope I tested correctly, I do not want to waste your time.''

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

Re: [Django] #31304: PostgreSQL full-text search employs coalesce function for non-null single-column searches with SearchVector

[Django]

#31304: PostgreSQL full-text search employs coalesce function for non-null 
single-
column searches with SearchVector
-+-
 Reporter:  Paul Boddie  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  PostgreSQL text  | Triage Stage:  Accepted
  search FTS coalesce SearchVector   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paul Boddie):

 Thanks for the comment, Simon.

 I wouldn't expect to_tsvector to treat an empty string and null in the
 same way - this being SQL after all - but the aim would be to avoid
 coalesce where null could never occur. This then becomes an issue of
 knowing when this might be guaranteed.

 I'm still getting familiar with the ORM, but I imagine that there could
 easily be cases where column values are null even if the table columns are
 declared not null. For instance, any query involving an outer join could
 produce null values for a "not null" column. In such cases, the
 characteristics of the output column would need to be defined by
 identifying its role in the query, pretty much as you say.

 I am inclined to think that making my own lookup would be the safest thing
 to do for now, with the lookups provided also considering the issue of
 transferring the configuration.

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

Re: [Django] #31308: Fixture loading fails when more than one Test case uses same fixtures

[Django]

#31308: Fixture loading fails when more than one Test case uses same fixtures
-+-
 Reporter:  Lokesh Gurram|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  2.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Testcases, fixtures  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Lokesh Gurram):

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


-- 
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/070.55c51b153fd2874178a6c075fb46a30a%40djangoproject.com.

Re: [Django] #31307: Arrow display error in filter_horizontal field when width less than 1024px

[Django]

#31307: Arrow display error in filter_horizontal field when width less than 
1024px
---+
 Reporter:  007|Owner:  007
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 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:  1
---+
Changes (by Carlton Gibson):

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

Re: [Django] #31185: fields.E310-E311 should take into account UniqueConstraints without conditions.

[Django]

#31185: fields.E310-E311 should take into account UniqueConstraints without
conditions.
-+-
 Reporter:  Pavel Garkin |Owner:  Ahmad
 |  Abdallah
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  UniqueConstraint | Triage Stage:  Accepted
  unique_together E310 E311  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Ahmad Abdallah):

 * 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.8f3237f93ab088479017dae850e2fda0%40djangoproject.com.

Re: [Django] #31304: PostgreSQL full-text search employs coalesce function for non-null single-column searches with SearchVector

[Django]

#31304: PostgreSQL full-text search employs coalesce function for non-null 
single-
column searches with SearchVector
-+-
 Reporter:  Paul Boddie  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  PostgreSQL text  | Triage Stage:  Accepted
  search FTS coalesce SearchVector   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Paul, I did more investigation and it looks like we can't also drop the
 `Coalesce` even in cases where there's a single expression and no
 concatenation needs to take place. The reason for that is that
 `to_tsvector('')` and `to_tsvector(null)` are not equivalent as the latter
 will result in SQL `Unknown` when used with the `@@` operator. That's
 problematic when negating expressions as both `to_tsvector(null) @@
 to_tsquery('test')` and `NOT to_tsvector(null) @@ to_tsquery('test')`
 result in the same value effectively breaking `~Q` and `exclude`.

 Regarding the `.null` handling I also did a bit of investigation and
 here's a case where checking for `output_field.null` would be a false
 negative


 {{{#!python
 class Manager(models.Model):
 name = models.TextField()

 class Store(models.Model):
 manager = models.ForeignKey(Manager)
 second_manager = models.ForeignKey(Manager, null=True)


 Store.objects.annotate(
 search=SearchVector('manager__name', 'second_manager__name')
 ).filter(search='Victor')
 }}}

 In this particular case the `Col` that `'second_manager__name'` resolves
 to would have `Manager.name` as `output_field` but it's not `null=True`
 even it's ''nullable'' if `store.second_manager is None`. In order to
 properly determine whether or not the expression should be coalesced we
 need to annotate `Col` with a flag that takes the whole relationship
 nullability in account.

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

[Django] #31308: Fixture loading fails when more than one Test case uses same fixtures

[Django]

#31308: Fixture loading fails when more than one Test case uses same fixtures
-+-
   Reporter:  Lokesh |  Owner:  nobody
  Gurram |
   Type:  Bug| Status:  new
  Component:  Testing|Version:  2.2
  framework  |
   Severity:  Normal |   Keywords:  Testcases, fixtures
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 If I have more than one TestCase using the same fixture, loading data
 between test cases raises unique constraint violation error on Postgres
 (works fine on SQLite)

 {{{
 class Test1(TestCase):
 fixtures = ['fixture.json']

 def test_demo(self):
 u = User.objects.get(username='testuser1')
 #some testing

 class Test2(TestCase):
 fixtures = ['fixture.json']

 def test_demo2(self):
 #some testing
 pass
 }}}

 **where my fixture.json is**
 Profile table has a one-to-one relation with User table.
 {{{
 [
 {
 "model": "app1.user",
 "pk": 1,
 "fields": {
 "password": "",
 "last_login": null,
 "is_superuser": false,
 "username": "testuser1",
 "first_name": "",
 "last_name": "",
 "is_staff": false,
 "is_active": true,
 "date_joined": "2020-02-21T12:59:17.302Z",
 "email": null,
 "groups": [],
 "user_permissions": []
 }
 },
 {
 "model": "app1.profile",
 "pk": 1,
 "fields": {
 "user": 1,
 "firebaseID": null,
 "phone": null,
 "completed_till": 0,
 }
 }
 ]

 }}}

 Running each Test Case separately works fine. But when we run them in one
 go, first Test case goes through and before the second test case executes,
 I get this error -

 {{{
 django.db.utils.IntegrityError: Problem installing fixture
 'C:\...\app1\fixtures\fixture.json': Could not load app1.Profile(pk=1):
 duplicate key value violates unique constraint "app1_profile_user_id_key"
 }}}


 Any idea why the DB is not completely cleared before trying to load the
 fixtures for the next TestCase. I tested this with Django 2.2 on Postgres
 10/12.  The problem persists in both.
 Interestingly though testing on SQLite doesn't give any problem.

-- 
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/055.206678b0dbf77429e6635752a53ace66%40djangoproject.com.

Re: [Django] #28280: numberformat.format() incorrectly formats large/tiny floats in scientific notation

[Django]

#28280: numberformat.format() incorrectly formats large/tiny floats in 
scientific
notation
---+--
 Reporter:  Wil Tan|Owner:  Hasan Ramezani
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  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


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

Re: [Django] #29129: Child model updates parent model with empty fields making an extra query in multi-inheritance when parent model has custom PK

[Django]

#29129: Child model updates parent model with empty fields making an extra 
query in
multi-inheritance when parent model has custom PK
-+-
 Reporter:  user0007 |Owner:  Abhijeet
 |  Viswa
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   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 Abhijeet Viswa):

 * owner:  nobody => Abhijeet Viswa
 * status:  new => assigned


Comment:

 Thank you. I'll come up with a patch soon.

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

Re: [Django] #29129: Child model updates parent model with empty fields making an extra query in multi-inheritance when parent model has custom PK

[Django]

#29129: Child model updates parent model with empty fields making an extra 
query in
multi-inheritance when parent model has custom PK
-+-
 Reporter:  user0007 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   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 Carlton Gibson):

 Cheers Simon.

 > I'm up for fixing this issue if it is accepted.

 Abhijeet, if you'd like to assign yourself and take a look that would be
 great. Reach out if you need any input.
 Thanks.

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

Re: [Django] #29129: Child model updates parent model with empty fields making an extra query in multi-inheritance when parent model has custom PK

[Django]

#29129: Child model updates parent model with empty fields making an extra 
query in
multi-inheritance when parent model has custom PK
-+-
 Reporter:  user0007 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   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 Simon Charette):

 Carlton, I agree that it's its own issue and that it's highly related to
 #18305.

 I'd say the fact that `save(force_insert=True)` doesn't work **is** a
 duplicate of #18305 and the fact `save()` doesn't result in the same
 optimization as #29260 when a primary key default is defined in MTI is an
 omission of #29260.

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

Re: [Django] #28280: numberformat.format() incorrectly formats large/tiny floats in scientific notation

[Django]

#28280: numberformat.format() incorrectly formats large/tiny floats in 
scientific
notation
---+--
 Reporter:  Wil Tan|Owner:  Hasan Ramezani
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  master
 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
 * version:  1.11 => 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/064.34066b3a6e0d4f21bb3a85902a9fa8d8%40djangoproject.com.

Re: [Django] #31291: Rename salt to mask in the context of CSRF tokens

[Django]

#31291: Rename salt to mask in the context of CSRF tokens
-+-
 Reporter:  Ram Rachum   |Owner:  Ram
 Type:   |  Rachum
  Cleanup/optimization   |   Status:  closed
Component:  CSRF |  Version:  3.0
 Severity:  Normal   |   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 GitHub ):

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


Comment:

 In [changeset:"5b09354954348f1a56df32b2d7dbe074a23a4532" 5b093549]:
 {{{
 #!CommitTicketReference repository=""
 revision="5b09354954348f1a56df32b2d7dbe074a23a4532"
 Fixed #31291 -- Renamed salt to mask for CSRF tokens.
 }}}

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

Re: [Django] #31291: Rename salt to mask in the context of CSRF tokens

[Django]

#31291: Rename salt to mask in the context of CSRF tokens
-+-
 Reporter:  Ram Rachum   |Owner:  Ram
 Type:   |  Rachum
  Cleanup/optimization   |   Status:  assigned
Component:  CSRF |  Version:  3.0
 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 felixxm):

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

Re: [Django] #31276: Add 'flush' option to only clear non-empty tables

[Django]

#31276: Add 'flush' option to only clear non-empty tables
-+-
 Reporter:  Adam (Chainz)|Owner:  jonatron
  Johnson|
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_docs:  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/068.15d33b03ab3197b950aae479c46db785%40djangoproject.com.

Re: [Django] #29129: Child model updates parent model with empty fields making an extra query in multi-inheritance when parent model has custom PK

[Django]

#29129: Child model updates parent model with empty fields making an extra 
query in
multi-inheritance when parent model has custom PK
-+-
 Reporter:  user0007 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   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 Abhijeet Viswa):

 * cc: Abhijeet Viswa (added)


Comment:

 CC'ing myself since I reported #31297. Didn't know about this ticket while
 creating that one.
 I'm up for fixing this issue if it is 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/066.57bc8fd41cd0767184cf45e189f51f21%40djangoproject.com.

Re: [Django] #29129: Child model updates parent model with empty fields making an extra query in multi-inheritance when parent model has custom PK

[Django]

#29129: Child model updates parent model with empty fields making an extra 
query in
multi-inheritance when parent model has custom PK
-+-
 Reporter:  user0007 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   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 Carlton Gibson):

 * cc: Simon Charette (added)
 * status:  closed => new
 * resolution:  duplicate =>


Comment:

 #31297 was opened and is a duplicate of this. This still occurs in Django
 3.0. Reproduced at a6b3938afc0204093b5356ade2be30b461a698c5. It looks like
 this use-case wasn't picked up as part of #29260. Possibly related to
 #18305.

 Simon, re-opening and CC-ing you to ask your opinion. (Thanks!)

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

Re: [Django] #31297: force_insert not respected by parent class with default primary key

[Django]

#31297: force_insert not respected by parent class with default primary key
-+-
 Reporter:  Abhijeet Viswa   |Owner:  Abhijeet
 |  Viswa
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  force_insert mti | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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


Comment:

 Thanks for the report.

 The force_insert is not needed in the example. The results are the same
 with and without it.

 The example is identical to #29129. We'll discuss there.

-- 
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/071.765af722f89a345db7b9e3ae1f4c2fa3%40djangoproject.com.

Re: [Django] #31307: Arrow display error in filter_horizontal field when width less than 1024px

[Django]

#31307: Arrow display error in filter_horizontal field when width less than 
1024px
---+
 Reporter:  007|Owner:  007
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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:  1
---+

Comment (by Carlton Gibson):

 Thanks for the extra screenshots. Yes, the hover state for the remove
 arrow should have the highlight. (I was looking for the misplacement.)

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

Re: [Django] #31293: MultiPartParser support double quotes

[Django]

#31293: MultiPartParser support double quotes
--+
 Reporter:  007   |Owner:  007
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  HTTP handling |  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 Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. First glance at the PR looks reasonable.

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

Re: [Django] #31304: PostgreSQL full-text search employs coalesce function for non-null single-column searches with SearchVector

[Django]

#31304: PostgreSQL full-text search employs coalesce function for non-null 
single-
column searches with SearchVector
-+-
 Reporter:  Paul Boddie  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  PostgreSQL text  | Triage Stage:  Accepted
  search FTS coalesce SearchVector   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


Comment:

 Accepting based on the discussion so far. Thanks both.

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

Re: [Django] #22841: ModelChoiceField does not make it easy to reuse querysets

[Django]

#22841: ModelChoiceField does not make it easy to reuse querysets
-+
 Reporter:  Marc Tamlyn  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   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 Carlton Gibson):

 * cc: Carlton Gibson (added)
 * owner:  Michael Vasiliou => (none)
 * status:  assigned => new


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

Re: [Django] #31295: required ModelChoiceField makes duplicate (cursor) queries to the database

[Django]

#31295: required ModelChoiceField makes duplicate (cursor) queries to the 
database
-+-
 Reporter:  Aurélien Pardon  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Forms|  Version:  2.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  Model| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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


Comment:

 Hi Aurélien,

 Using the iterator was a deliberate design choice. (Placing your
 suggestion in causes tests failure, including `test_choices_freshness` in
 line with this.)

 The use to point to in `Select.use_required_attribute()` shouldn't be
 problematic, since
 
[https://github.com/django/django/blob/271fdab8b78af558238df51c64b4d1c8dd0792bb/django/forms/widgets.py#L555-L560
 `self.choices` is fully evaluated in `ChoiceWidget.__init__()`], as per
 the comment there, precisely to allow repeated iteration.

 I think the underlying issue here is probably #22841.

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

Re: [Django] #31304: PostgreSQL full-text search employs coalesce function for non-null single-column searches with SearchVector

[Django]

#31304: PostgreSQL full-text search employs coalesce function for non-null 
single-
column searches with SearchVector
-+-
 Reporter:  Paul Boddie  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  PostgreSQL text  | Triage Stage:
  search FTS coalesce SearchVector   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paul Boddie):

 The motivation for eliminating coalesce is that it is superfluous when
 searching a non-null column already indexed appropriately. I accept that
 in the general case, where people may be combining columns, there may be a
 need to coalesce null values, but I would regard it as pretty inelegant to
 have to create an index coalescing values that would never be null. (One
 might argue that PostgreSQL could itself eliminate any redundant coalesce
 operation specified for an index, and I don't know why it doesn't in this
 case.)

 The suggestion to make the search lookup employ any indicating
 configuration from the operand is a good one. Indeed, it surprises me that
 this isn't already done because it appears to be an easy mistake when
 manually preparing queries that could be eliminated in a framework like
 this.

 I'll try and make a pull request on GitHub.

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

Re: [Django] #31307: Arrow display error in filter_horizontal field when width less than 1024px

[Django]

#31307: Arrow display error in filter_horizontal field when width less than 
1024px
---+
 Reporter:  007|Owner:  007
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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:  1
---+

Comment (by 007):

 Replying to [comment:3 Carlton Gibson]:
 > Yes, thanks for the report. I'm seeing this only for the Choose arrow,
 and not for Remove.
 >
 > [https://github.com/django/django/pull/12490/files PR].
 This pr changed  `.active.selector-remove:focus, .active.selector-
 remove:hover` and `.active.selector-add:focus, .active.selector-add:hover`

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

Re: [Django] #31307: Arrow display error in filter_horizontal field when width less than 1024px

[Django]

#31307: Arrow display error in filter_horizontal field when width less than 
1024px
---+
 Reporter:  007|Owner:  007
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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:  1
---+
Changes (by 007):

 * Attachment "less_767_hover_remove_expected.png" 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/064.b05bd4a5fd4697c29671a3006d1a502a%40djangoproject.com.

Re: [Django] #31307: Arrow display error in filter_horizontal field when width less than 1024px

[Django]

#31307: Arrow display error in filter_horizontal field when width less than 
1024px
---+
 Reporter:  007|Owner:  007
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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:  1
---+
Changes (by 007):

 * Attachment "less_767_hover_remove_current.png" 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/064.f74c5d689b337f09d90b059f99de1842%40djangoproject.com.

Re: [Django] #31307: Arrow display error in filter_horizontal field when width less than 1024px

[Django]

#31307: Arrow display error in filter_horizontal field when width less than 
1024px
---+
 Reporter:  007|Owner:  007
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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:  1
---+
Changes (by 007):

 * Attachment "767_1024_hover_remove_expected.png" 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/064.f3e81fa9d7975bd33f064067f513473f%40djangoproject.com.

Re: [Django] #31307: Arrow display error in filter_horizontal field when width less than 1024px

[Django]

#31307: Arrow display error in filter_horizontal field when width less than 
1024px
---+
 Reporter:  007|Owner:  007
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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:  1
---+
Changes (by 007):

 * Attachment "767_1024_hover_remove_current .png" 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/064.398c1fb105d01350f7fad8bd0da520e7%40djangoproject.com.

Re: [Django] #31307: Arrow display error in filter_horizontal field when width less than 1024px

[Django]

#31307: Arrow display error in filter_horizontal field when width less than 
1024px
---+
 Reporter:  007|Owner:  007
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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:  1
---+
Changes (by Carlton Gibson):

 * stage:  Unreviewed => Accepted


Old description:

> when screen width less than 1024  filter_horizontal field add and remove
> arrow display error when mouth hover

New description:

 when screen width less than 1024  filter_horizontal field add and remove
 arrow display error when mouse hover

--

Comment:

 Yes, thanks for the report. I'm seeing this only for the Choose arrow, and
 not for Remove.

 [https://github.com/django/django/pull/12490/files 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.3d4acb5ef09ffe452dd9a9e2ee693da1%40djangoproject.com.