[Django] #35438: Failed to insert an model instance into db that utilizes a UUID as its primary key and incorporates a GeneratedField.

[Django]

#35438: Failed to insert an model instance into db that utilizes a UUID as its
primary key and incorporates a GeneratedField.
-+
   Reporter:  长孙弘奕   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  5.0
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I have defined a model that employs a UUIDField as its primary key,
 accompanied by a JSONField and several GeneratedFields, which are intended
 for indexing the JSONFields. However, when attempting to load data via
 loaddata from a JSON fixture, the process fails during the execution of
 the execute_sql method within django/db/models/SQL/compiler.py. The
 problematic code snippet is as follows:

 {{{
 def execute_sql(self, returning_fields=None):
 
 if not self.returning_fields:
 return []

 else:
 cols = [opts.pk.get_col(opts.db_table)]
 rows = [
 (
 self.connection.ops.last_insert_id(
 cursor,
 opts.db_table,
 opts.pk.column,
 ),
 )
 ]
 converters = self.get_converters(cols)
 if converters:
 rows = list(self.apply_converters(rows, converters))
 return rows
 }}}


 Here, returning_fields comprises GeneratedFields, thereby preventing the
 method from directly returning an empty list at the outset of its logical
 execution. Moreover, since the model's primary key is not an
 AUTO_INCREMENT column (it's a UUID), last_insert_id() erroneously returns
 0. This subsequently triggers an error within self.apply_converters(rows,
 converters) as it attempts to treat 0 as a UUID.

 To address this issue, the else block logic requires adjustment to
 accommodate the presence of GeneratedField. Alternatively, within
 django/db/models/base.py's _save_table method, one could exclude
 GeneratedField from returning_fields. A modified approach might resemble:


 {{{
#Original: returning_fields = meta.db_returning_fields
 returning_fields = [ f for f in meta.db_returning_fields if
 not f.generated]
 results = self._do_insert(
 cls._base_manager, using, fields, returning_fields, raw
 )
 if results:
 for value, field in zip(results[0], returning_fields):
 setattr(self, field.attname, value)
 return updated
 }}}

 This adjusted strategy has proven effective in my project, successfully
 circumventing the aforementioned issues without introducing new problems.
-- 
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/0107018f56b747ec-b2a33923-b834-41c7-92ed-29d5c46232ff-00%40eu-central-1.amazonses.com.

Re: [Django] #35339: Ordering and filtering a Postgres ArrayAgg with parameters inverts SQL param order

[Django]

#35339: Ordering and filtering a Postgres ArrayAgg with parameters inverts SQL
param order
-+-
 Reporter:  Chris M  |Owner:  Chris M
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgres arrayagg| Triage Stage:  Ready for
  ordering   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Chris M):

 Simon, I am interested in working on the second phase of merging in
 `OrderableAggMixin` . I started playing around with this code, and I think
 it makes sense. My initial question is around how moving this up looks
 with regards to things like `ArrayAgg`. That function directly exists in
 other databases, like Sqlite, so would we want to put it into the core
 aggregate module instead of the postgres module? To build on that, MySQL
 implements basically the same behavior as `group_concat`, which Sqlite
 also supports, so is there some nuance to how that should be handled as
 well?

 Also, should we create a new ticket for this second phase of the work?
 What would that look like?
-- 
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/0107018f560b8142-1385fd95-f031-4b56-a934-fb85fba41e25-00%40eu-central-1.amazonses.com.

Re: [Django] #12978: Support in syndication framework for CSS stylesheet links

[Django]

#12978: Support in syndication framework for CSS stylesheet links
-+-
 Reporter:  intrepidweb  |Owner:  Baptiste
 |  Mispelon
 Type:  New feature  |   Status:  assigned
Component:  contrib.syndication  |  Version:  1.1
 Severity:  Normal   |   Resolution:
 Keywords:  syndication css  | Triage Stage:  Accepted
  stylesheets|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Baptiste Mispelon):

 * easy:   => 0
 * needs_better_patch:  1 => 0
 * ui_ux:   => 0

Comment:

 I've added support for CSS stylesheets as well and updated 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018f552aa46c-4c129609-b176-48b4-9f51-6f8746b5163b-00%40eu-central-1.amazonses.com.

Re: [Django] #35404: Admin fieldset multiple flexbox regressions

[Django]

#35404: Admin fieldset multiple flexbox regressions
+
 Reporter:  minusf  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  css admin fieldset  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  1
+
Changes (by minusf):

 * Attachment "admin-help-text.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/0107018f54d6e73f-1aabb949-6089-44c6-827d-f08256dd6538-00%40eu-central-1.amazonses.com.

Re: [Django] #35404: Admin fieldset multiple flexbox regressions

[Django]

#35404: Admin fieldset multiple flexbox regressions
+
 Reporter:  minusf  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  css admin fieldset  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  1
+
Changes (by minusf):

 * Attachment "Screenshot 2024-05-07 at 22.53.11.png" removed.

-- 
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/0107018f54d65980-22c3999f-d09a-4479-9c9e-9b83a9e10010-00%40eu-central-1.amazonses.com.

Re: [Django] #35404: Admin fieldset multiple flexbox regressions

[Django]

#35404: Admin fieldset multiple flexbox regressions
+
 Reporter:  minusf  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  css admin fieldset  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  1
+
Changes (by minusf):

 * Attachment "Screenshot 2024-05-07 at 22.53.11.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/0107018f54d6300e-5578dd9d-4e98-45e5-ad7d-1ac36f2438d6-00%40eu-central-1.amazonses.com.

Re: [Django] #35404: Admin fieldset multiple flexbox regressions

[Django]

#35404: Admin fieldset multiple flexbox regressions
+
 Reporter:  minusf  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  css admin fieldset  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  1
+
Comment (by minusf):

 > I think you can also remove the line-height

 I might be wrong but afaik multiline paragraphs strongly benefit in
 readability with `line-height` at least `1.2` to `1.5` depending on font
 type... This is an actual issue in the admin how it shows `help_text` as
 well and I meant to send a patch for that for years...
-- 
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/0107018f54d5e5bb-93621a64-81ca-483e-91f4-14e8d9351d2f-00%40eu-central-1.amazonses.com.

Re: [Django] #35381: Regression on json null value constraints in django 4.2

[Django]

#35381: Regression on json null value constraints in django 4.2
-+-
 Reporter:  Olivier Tabone   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.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):

 > I think we should reserve None only to represent SQL's NULL, and have a
 representation for the (string) json's null (I understand this matches the
 new JSONNull expression you are proposing).

 Yes it matches the `JSONNull` proposal. If we take away the ability to use
 `None` for filtering against JSON `null` we should provide an alternative.

 The deprecation could look like

 1. Introduce `JSONNull`
 2. Make `filter(jsonfield=None)` raise a deprecation warning pointing at
 either using `filter(jsonfield__isnull=True)` or
 `filter(jsonfield=JSONNull)`
 3. At the end of the deprecation period switch `filter(jsonfield=None)` to
 mean `filter(jsonfield__isnull=True)` link on all other fields

 It leaves the problem of having JSON `null` not surviving a round trip to
 the database as both SQL `NULL` and `json.loads("null")` are turned into
 Python `None` but that's a different issue that can be addressed with a
 specialized `decoder` if users require it.

 > Would this lookup allow further lookups to be chained?

 It could or not, what gets returned from a lookup can be prevent further
 chaining if we want.
-- 
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/0107018f53e6fb74-1b52bc9c-0cb9-475f-b8de-a122ccf56494-00%40eu-central-1.amazonses.com.

Re: [Django] #35381: Regression on json null value constraints in django 4.2

[Django]

#35381: Regression on json null value constraints in django 4.2
-+-
 Reporter:  Olivier Tabone   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.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 Natalia Bidart):

 Thank you Simon. In my view, and in an ideal situation, we shouldn't allow
 "anywhere" to use `None` as the json's `null`. I think we should reserve
 `None` only to represent SQL's `NULL`, and have a representation for the
 (string) json's `null` (I understand this matches the new `JSONNull`
 expression you are proposing).

 > Should we only do this at the top level to still allow
 `jsonfield__key=None` to filter against null keys?

 I would say no, because it then gets very confusing.

 > An alternative would be to introduce a `__jsonnull` lookup.

 Would this lookup allow further lookups to be chained?
-- 
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/0107018f5304d6c3-0b343c68-e274-4a3b-badd-fb16bb93739e-00%40eu-central-1.amazonses.com.

Re: [Django] #35407: Cache Model._meta.swapped

[Django]

#35407: Cache Model._meta.swapped
-+-
 Reporter:  Adam Johnson |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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
-+-
Changes (by Sarah Boyce <42296566+sarahboyce@…>):

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

Comment:

 In [changeset:"7abe5112f4cb50c15b79a2afd4c1b68f0767b243" 7abe511]:
 {{{#!CommitTicketReference repository=""
 revision="7abe5112f4cb50c15b79a2afd4c1b68f0767b243"
 Fixed #35407 -- Cached model's Options.swapped.
 }}}
-- 
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/0107018f5304ab33-350569fb-acde-4f04-806e-42e44eb48339-00%40eu-central-1.amazonses.com.

Re: [Django] #35331: Adding a new related entry using the "+" sign from M2M field doesn't update lists.

[Django]

#35331: Adding a new related entry using the "+" sign from M2M field doesn't 
update
lists.
---+--
 Reporter:  devin13cox |Owner:  devin13cox
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  5.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  1
---+--
Changes (by Sarah Boyce):

 * 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/0107018f52fe143a-f6cc57cc-1bd5-4cf6-9abb-51df26ce9c46-00%40eu-central-1.amazonses.com.

Re: [Django] #35414: Issue with AsyncClient ignoring default headers compared to synchronous Client

[Django]

#35414: Issue with AsyncClient ignoring default headers compared to synchronous
Client
-+-
 Reporter:  설원준(Wonjoon   |Owner:  nobody
  Seol)/Dispatch squad   |
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  AsyncClient, | Triage Stage:
  ASGIRequest|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by 설원준(Wonjoon Seol)/Dispatch squad):

 * resolution:  invalid =>
 * status:  closed => 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/0107018f52aabc51-3ceb254a-c0b3-4c0f-9582-d8f0e91c16d0-00%40eu-central-1.amazonses.com.

Re: [Django] #35425: .save(force_update=True) not respected for model instances with default primary keys

[Django]

#35425: .save(force_update=True) not respected for model instances with default
primary keys
-+-
 Reporter:  Jacob Walls  |Owner:  Jacob
 |  Walls
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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
-+-
Changes (by Sarah Boyce <42296566+sarahboyce@…>):

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

Comment:

 In [changeset:"ceea86baa36b91d0002911770340a2d7bd4f64b7" ceea86b]:
 {{{#!CommitTicketReference repository=""
 revision="ceea86baa36b91d0002911770340a2d7bd4f64b7"
 Fixed #35425 -- Avoided INSERT with force_update and explicit pk.

 Affected models where the primary key field is defined with a
 default or db_default, such as UUIDField.
 }}}
-- 
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/0107018f528d24ec-b78d1021-54a4-4705-b75e-60bab6661090-00%40eu-central-1.amazonses.com.

Re: [Django] #35430: Documentation about timezone is misleading

[Django]

#35430: Documentation about timezone is misleading
--+
 Reporter:  younes-chaoui |Owner:  い。
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Sarah Boyce):

 * 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/0107018f52884871-416599c6-70dd-4d95-aae4-99a74c3d4fcb-00%40eu-central-1.amazonses.com.

Re: [Django] #35430: Documentation about timezone is misleading

[Django]

#35430: Documentation about timezone is misleading
--+
 Reporter:  younes-chaoui |Owner:  い。
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Sarah Boyce):

 * 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/0107018f526a0140-70abc367-c829-4e28-a372-af294893a349-00%40eu-central-1.amazonses.com.

Re: [Django] #35407: Cache Model._meta.swapped

[Django]

#35407: Cache Model._meta.swapped
-+-
 Reporter:  Adam Johnson |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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 Sarah Boyce):

 * 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/0107018f52405760-bb7e9cf3-4e09-414a-9792-40cf4b90e809-00%40eu-central-1.amazonses.com.

Re: [Django] #35434: prefetch_related_objects fails to cache UUID FKs when the string representation of a UUID is used

[Django]

#35434: prefetch_related_objects fails to cache UUID FKs when the string
representation of a UUID is used
-+-
 Reporter:  Selcuk Ayguney   |Owner:  (none)
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  dev
 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
-+-
Changes (by Sarah Boyce):

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

Comment:

 Hi all, currently closing as "needsinfo". It's not clear to me where in
 the docs you're hoping to add something or what would have been useful in
 the docs for this case. Can you share an idea of what you have in mind?
-- 
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/0107018f521402d5-3d9b18d2-02fa-4ad4-895e-c7556e8e7d2b-00%40eu-central-1.amazonses.com.

Re: [Django] #35423: Show which fields are being searched in Admin change_list's `search_fields`

[Django]

#35423: Show which fields are being searched in Admin change_list's 
`search_fields`
-+-
 Reporter:  Ren de la Cruz   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  admin,   | Triage Stage:  Accepted
  search_fields, change_list,|
  search, ui |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Comment (by Rajeesh Punathil):

 Yes, this can be quickly added as a small help text below and I tried that
 but what about values like {{{user__email, name__exact, ^question,
 @descr}}}, etc? We may need to use verbose equivalents for each, because
 the admin staff may not have technical knowledge to understand them as
 they are given. What's the suggestion?
-- 
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/0107018f51beef80-4c888db6-ba40-422e-8d69-6e603be1f9b7-00%40eu-central-1.amazonses.com.

Re: [Django] #35430: Documentation about timezone is misleading

[Django]

#35430: Documentation about timezone is misleading
--+
 Reporter:  younes-chaoui |Owner:  い。
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Comment (by い。):

 Hello,

 This is my first contribution to this project, and I'm excited to be a
 part of this community. I've submitted a pull request to address the issue
 detailed in ticket #35430, aiming to correct the documentation regarding
 time zone handling in Django. I would appreciate any feedback or
 suggestions for improvement as I'm eager to learn and contribute
 effectively. Thank you for reviewing my changes!

 Best regards,
 username: koupro0204
 https://github.com/django/django/pull/18138
-- 
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/0107018f51aed82c-74eea74a-3b02-4989-80c2-9de0fd376a24-00%40eu-central-1.amazonses.com.

Re: [Django] #35430: Documentation about timezone is misleading

[Django]

#35430: Documentation about timezone is misleading
--+
 Reporter:  younes-chaoui |Owner:  い。
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by い。):

 * 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/0107018f51ab80e0-f340b1f4-853a-4e80-acb5-7cf4d6ffc26f-00%40eu-central-1.amazonses.com.