Re: [Django] #35370: `context["debug"] is not settings.DEBUG` and the future of `django.templates.context_processors.debug`: (was: `request.context["debug"] is not settings.DEBUG` and the future of `d

[Django]

#35370: `context["debug"] is not settings.DEBUG` and the future of
`django.templates.context_processors.debug`:
-+-
 Reporter:  Marc Gibbons |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  context processors,  | Triage Stage:
  internal ips, debug, template  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Marc Gibbons):

 * summary:
 `request.context["debug"] is not settings.DEBUG` and the future of
 `django.templates.context_processors.debug`:
 =>
 `context["debug"] is not settings.DEBUG` and the future of
 `django.templates.context_processors.debug`:

-- 
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/0107018ed52c0ae3-49e4ad71-83fe-41d5-99c4-fc41f4e6c85b-00%40eu-central-1.amazonses.com.

[Django] #35370: `request.context["debug"] is not settings.DEBUG` and the future of `django.templates.context_processors.debug`:

[Django]

#35370: `request.context["debug"] is not settings.DEBUG` and the future of
`django.templates.context_processors.debug`:
-+-
   Reporter:  Marc   |  Owner:  nobody
  Gibbons|
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Template   |Version:  5.0
  system |   Keywords:  context processors,
   Severity:  Normal |  internal ips, debug, template
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I went down a rabbit hole recently with the
 [https://docs.djangoproject.com/en/5.0/ref/templates/api/#django-template-
 context-processors-debug: django.templates.context_processors.debug]
 context processor.

 What I was looking for:
 - A context variable called `debug` which is always present
 -  `context['debug'] is True` when `settings.DEBUG = True`  and
 `context['debug'] is False` when `settings.DEBUG = False`

 What I got:
 - A context variable named `debug` is sometimes included, but only when
 both `settings.DEBUG` is `True` and if `request.META['REMOTE_ADDR'] in
 settings.INTERNAL_IPS`. In other words, `debug` exists and is true only
 when your project has `DEBUG` turned on AND you’re visiting from an
 allowed list of IPs.
 - A context variable named `sql_queries` lazily returns all SQL queries
 executed in the request for the purpose of profiling.

 Some context:
 - This context variable `debug` and its assignment is as old as Django. It
 appears in one of the first
 
[https://github.com/django/django/commit/ed114e15106192b22ebb78ef5bf5bce72b419d13
 #diff-
 27135de559ecc2dc3f2548d6ce5cbc8495de0acf053c0b0d4d77e642b463f6beR16-R19:
 commits ever], and aside from being moved around over the years, has
 remained unchanged.
 - In no other area of Django is `INTERNAL_IPS` used to determine if you’re
 in `DEBUG` – this is an outlier.

 Ideally, `debug` in templates would have the same meaning as it does in
 Python / the rest of the framework. Example:

 {{{#!python
 def debug(request):
 return {"debug": settings.DEBUG}
 }}}

 Changing the context processor this way could be catastrophic.

 Some thoughts:
 - `debug`, and its evaluation (when present) in request context is
 confusing (at least to me).
 - This context processor has a variety of concerns: evaluating DEBUG,
 determining if you’re trusted on a network, and gathering SQL queries.
 Would it make sense to split it up accordingly?
 - Or, given the risk security of changing how `debug` evaluates, could the
 entire context processor be marked for deprecation? Profiling SQL queries
 could be left to third party libraries like django-debug-toolbar.
 - `INTERNAL_IPS` might also be a candidate for deprecation.
-- 
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/0107018ed520202f-9cabd18f-057c-4574-b218-881a52541708-00%40eu-central-1.amazonses.com.

Re: [Django] #34917: Links in the Django admin should be underlined.

[Django]

#34917: Links in the Django admin should be underlined.
-+-
 Reporter:  Dmitriy Chukhin  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  anchor |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Tim Graham):

 * needs_better_patch:  1 => 0

Comment:

 I believe the [https://github.com/django/django/pull/17883 PR] is awaiting
 review.
-- 
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/0107018ed4fb4ab8-fccdfd96-e1a1-4f66-bbb8-3c82a8b9091b-00%40eu-central-1.amazonses.com.

Re: [Django] #34917: Links in the Django admin should be underlined.

[Django]

#34917: Links in the Django admin should be underlined.
-+-
 Reporter:  Dmitriy Chukhin  |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  anchor |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by avish mehta):

 * owner:  avish mehta => (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/0107018ed4f319cf-f98f61e4-944e-4dba-ba8a-5223daf24c56-00%40eu-central-1.amazonses.com.

Re: [Django] #34917: Links in the Django admin should be underlined.

[Django]

#34917: Links in the Django admin should be underlined.
-+-
 Reporter:  Dmitriy Chukhin  |Owner:  avish
 Type:   |  mehta
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  anchor |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by avish mehta):

 * owner:  nobody => avish mehta
 * status:  new => assigned

-- 
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/0107018ed4eefb07-583e1b6c-bcfe-464c-968b-367bce6b5551-00%40eu-central-1.amazonses.com.

Re: [Django] #35358: Rename BaseConstraint._check() to check()

[Django]

#35358: Rename BaseConstraint._check() to check()
-+-
 Reporter:  Simon Charette   |Owner:  avish
 Type:   |  mehta
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  6.0  | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Simon Charette):

 To make it clear, this ticket cannot be worked on until Django 6.0 which
 will remove the deprecation shim for `CheckConstraint.check` in favor of
 `.condition` which will allow `BaseConstraint.check` to be reclaimed.
-- 
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/0107018ed4e95816-096add39-c70f-4a6c-a2e9-a9bd44b1957c-00%40eu-central-1.amazonses.com.

Re: [Django] #35358: Rename BaseConstraint._check() to check()

[Django]

#35358: Rename BaseConstraint._check() to check()
-+-
 Reporter:  Simon Charette   |Owner:  avish
 Type:   |  mehta
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  6.0  | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by avish mehta):

 * owner:  (none) => avish mehta
 * status:  new => assigned

-- 
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/0107018ed4caad8a-89cd34df-edfb-437d-917b-d43d88959636-00%40eu-central-1.amazonses.com.

Re: [Django] #35358: Rename BaseConstraint._check() to check()

[Django]

#35358: Rename BaseConstraint._check() to check()
-+-
 Reporter:  Simon Charette   |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  6.0  | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by avish mehta):

 * owner:  avish mehta => (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/0107018ed4ca658c-a8d21d7d-7d65-4cfa-8bc2-f60a5270415c-00%40eu-central-1.amazonses.com.

Re: [Django] #35358: Rename BaseConstraint._check() to check()

[Django]

#35358: Rename BaseConstraint._check() to check()
-+-
 Reporter:  Simon Charette   |Owner:  avish
 Type:   |  mehta
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  6.0  | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by avish mehta):

 * owner:  nobody => avish mehta
 * status:  new => assigned

-- 
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/0107018ed4c8af31-fb96bb01-d3d2-42dd-9962-2aea5138cf4f-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+
 Reporter:  damoncheng|Owner:  Csirmaz Bendegúz
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Natalia Bidart):

 * resolution:   => wontfix
 * stage:  Someday/Maybe => Unreviewed
 * status:  assigned => closed

Comment:

 Replying to [comment:14 Csirmaz Bendegúz]:
 > I have submitted a patch: https://github.com/django/django/pull/18053

 As said in the [https://forum.djangoproject.com/t/custom-group-model/30070
 forum post], thank you so much Csirmaz for your work on this.
 Nevertheless, following the forum and previous conversations, I'll be
 closing this as wontfix.
-- 
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/0107018ed40a9f06-061a190b-0b49-41c5-82a0-098b1eb7c6e1-00%40eu-central-1.amazonses.com.

Re: [Django] #34789: `filter_horizontal` duplicates entries in "Chosen" column after instance is added via in another field using the "plus" JS action

[Django]

#34789: `filter_horizontal` duplicates entries in "Chosen" column after 
instance is
added via in another field using the "plus" JS action
---+--
 Reporter:  devin13cox |Owner:  devin13cox
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 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 devin13cox):

 * 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/0107018ed3a5dfc3-1968017e-65bb-47bd-b164-0fd04f3071c2-00%40eu-central-1.amazonses.com.

Re: [Django] #35235: ArrayAgg() doesn't return default when filter contains __in=[].

[Django]

#35235: ArrayAgg() doesn't return default when filter contains __in=[].
--+--
 Reporter:  Per Carlsen   |Owner:  Sharon Woo
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:  ArrayAgg  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Natalia Bidart):

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

Comment:

 [https://github.com/django/django/pull/17890 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/0107018ed36d70d0-1ab2a922-1d21-44cc-b9dd-14f106545f05-00%40eu-central-1.amazonses.com.

Re: [Django] #35235: ArrayAgg() doesn't return default when filter contains __in=[].

[Django]

#35235: ArrayAgg() doesn't return default when filter contains __in=[].
--+--
 Reporter:  Per Carlsen   |Owner:  Sharon Woo
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:  ArrayAgg  | 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):

 Hi Per, the current status of the ticket is reflected in the ticket
 history, where all conversations are documented openly.

 We greatly rely on the community for contributing both fixes and new
 features. If you have the time and desire to help, there is an ongoing
 effort from Sharon Woo in this PR:

 https://github.com/django/django/pull/17890

 One option would be to reach out to Sharon Woo and confirm whether they
 have time to continue working in the PR and see if/where you could be of
 help. If they don't, perhaps pick up where they left of? From a quick
 read, it seems that the bulk of the work was done, only some extra tests
 are needed.

 Thank you!
-- 
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/0107018ed36d0c21-c2d877ed-c5b7-4f3b-afe6-5a5e46da01c5-00%40eu-central-1.amazonses.com.

Re: [Django] #32831: Some cache tests are flaky (e.g. cache.tests.BaseMemcachedTests.test_touch)

[Django]

#32831: Some cache tests are flaky (e.g. 
cache.tests.BaseMemcachedTests.test_touch)
--+
 Reporter:  Chris Jerdonek|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Cache system)   |  Version:  dev
 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):

 Another one, different but similar:
 {{{
 ...
 Using shuffle seed: 5526860306 (generated)
 ...
 ==
 ERROR [0.003s]: test_lru_incr (cache.tests.LocMemCacheTests.test_lru_incr)
 --
 Traceback (most recent call last):
   File "/home/jenkins/workspace/main-
 random/database/spatialite/label/focal/python/python3.12/django/test/utils.py",
 line 446, in inner
 return func(*args, **kwargs)
^
   File "/home/jenkins/workspace/main-
 random/database/spatialite/label/focal/python/python3.12/tests/cache/tests.py",
 line 1433, in test_lru_incr
 self.assertEqual(cache.incr(key), key + 1)
  ^^^
   File "/home/jenkins/workspace/main-
 
random/database/spatialite/label/focal/python/python3.12/django/core/cache/backends/locmem.py",
 line 70, in incr
 raise ValueError("Key '%s' not found" % key)
 ValueError: Key ':1:0' not found

 --
 Ran 17776 tests in 1566.550s

 FAILED (errors=1, skipped=1161, expected failures=5)
 }}}
-- 
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/0107018ed35b4901-bbb9a641-9277-41dd-b4e0-0ecdb13248f2-00%40eu-central-1.amazonses.com.

Re: [Django] #28519: Add filter(), exclude(), and other base QuerySet methods to combined QuerySets (union(), etc.)

[Django]

#28519: Add filter(), exclude(), and other base QuerySet methods to combined
QuerySets (union(), etc.)
-+-
 Reporter:  Stanislav Karpov |Owner:  Damir
 |  Nafikov
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  union,   | Triage Stage:  Accepted
  intersection, difference   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Simon Charette):

 Closed #35369 for the `aggregate` method.
-- 
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/0107018ed35a5ef2-bf8bd002-092f-4c89-a5e7-854e329f7386-00%40eu-central-1.amazonses.com.

Re: [Django] #35369: MySQL .union().aggregate() raises Unknown Column

[Django]

#35369: MySQL .union().aggregate() raises Unknown Column
-+-
 Reporter:  DS/Charlie   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
  union,aggregate,mysql  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

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

Comment:

 Per
 
[https://docs.djangoproject.com/en/5.0/ref/models/querysets/#django.db.models.query.QuerySet.union
 the documentation]

 > In addition, only LIMIT, OFFSET, COUNT(*), ORDER BY, and specifying
 columns (i.e. slicing, count(), exists(), order_by(), and
 values()/values_list()) are allowed on the resulting QuerySet. Further,
 databases place restrictions on what operations are allowed in the
 combined queries.

 Closing as duplicate of #28519.
-- 
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/0107018ed359f109-7d3b-9eeb-45db-adca-ad9e7c6f7a3b-00%40eu-central-1.amazonses.com.

Re: [Django] #35369: MySQL .union().aggregate() raises Unknown Column

[Django]

#35369: MySQL .union().aggregate() raises Unknown Column
-+-
 Reporter:  DS/Charlie   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  union,aggregate,mysql  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by DS/Charlie:

Old description:

> {{{
>
> class BugModel(models.Model):
> foo = models.CharField(max_length=255)
>
> class BugTestCase(TestCase):
> def test_bug(self):
> a = BugModel.objects.all()
> b = BugModel.objects.all()
>
> ab = a.union(b)
> """
> (
> SELECT `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> ) UNION (
> SELECT `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> )
> """
>
> ab.aggregate(max=Max("foo"))
> """
> SELECT MAX(`__col1`)
> FROM (
> (
> SELECT  `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> ) UNION (
> SELECT `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> )
> ) subquery
>

> Traceback (most recent call last):
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/django/db/backends/utils.py", line 89, in _execute
> return self.cursor.execute(sql, params)
>
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/django/db/backends/mysql/base.py", line 75, in execute
> return self.cursor.execute(query, args)
>
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/MySQLdb/cursors.py", line 179, in execute
> res = self._query(mogrified_query)
>   
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/MySQLdb/cursors.py", line 330, in _query
> db.query(q)
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/MySQLdb/connections.py", line 261, in query
> _mysql.connection.query(self, query)
> MySQLdb.OperationalError: (1054, "Unknown column '__col1' in
> 'field list'")
> """
> }}}
>

> Django 4.2.11 and 5.0.4
> mysqlclient 2.2.4
>
> all in a clean virtualenv on python 3.12.2

New description:

 {{{

 class BugModel(models.Model):
 foo = models.CharField(max_length=255)

 class BugTestCase(TestCase):
 def test_bug(self):
 a = BugModel.objects.all()
 b = BugModel.objects.all()

 ab = a.union(b)   # does NOT happen with `a | b`
 """
 (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 ) UNION (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 )
 """

 q = ab.aggregate(max=Max("foo"))
 """
 SELECT MAX(`__col1`)
 FROM (
 (
 SELECT  `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 ) UNION (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 )
 ) subquery


 Traceback (most recent call last):
   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/django/db/backends/utils.py", line 89, in _execute
 return self.cursor.execute(sql, params)

   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/django/db/backends/mysql/base.py", line 75, in execute
 return self.cursor.execute(query, args)

   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/MySQLdb/cursors.py", line 179, in execute
 res = self._query(mogrified_query)
   

Re: [Django] #35369: MySQL .union().aggregate() raises Unknown Column

[Django]

#35369: MySQL .union().aggregate() raises Unknown Column
-+-
 Reporter:  DS/Charlie   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  union,aggregate,mysql  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by DS/Charlie:

Old description:

> {{{
>
> class BugModel(models.Model):
> foo = models.CharField(max_length=255)
>
> class BugTestCase(TestCase):
> def test_bug(self):
> a = BugModel.objects.all()
> b = BugModel.objects.all()
>
> ab = a.union(b, all=False)
> """
> (
> SELECT `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> ) UNION (
> SELECT `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> )
> """
>
> ab.aggregate(max=Max("foo"))
> """
> SELECT MAX(`__col1`)
> FROM (
> (
> SELECT  `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> ) UNION (
> SELECT `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> )
> ) subquery
>

> Traceback (most recent call last):
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/django/db/backends/utils.py", line 89, in _execute
> return self.cursor.execute(sql, params)
>
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/django/db/backends/mysql/base.py", line 75, in execute
> return self.cursor.execute(query, args)
>
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/MySQLdb/cursors.py", line 179, in execute
> res = self._query(mogrified_query)
>   
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/MySQLdb/cursors.py", line 330, in _query
> db.query(q)
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/MySQLdb/connections.py", line 261, in query
> _mysql.connection.query(self, query)
> MySQLdb.OperationalError: (1054, "Unknown column '__col1' in
> 'field list'")
> """
> }}}
>

> Django 4.2.11 and 5.0.4
> mysqlclient 2.2.4
>
> all in a clean virtualenv on python 3.12.2

New description:

 {{{

 class BugModel(models.Model):
 foo = models.CharField(max_length=255)

 class BugTestCase(TestCase):
 def test_bug(self):
 a = BugModel.objects.all()
 b = BugModel.objects.all()

 ab = a.union(b)
 """
 (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 ) UNION (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 )
 """

 ab.aggregate(max=Max("foo"))
 """
 SELECT MAX(`__col1`)
 FROM (
 (
 SELECT  `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 ) UNION (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 )
 ) subquery


 Traceback (most recent call last):
   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/django/db/backends/utils.py", line 89, in _execute
 return self.cursor.execute(sql, params)

   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/django/db/backends/mysql/base.py", line 75, in execute
 return self.cursor.execute(query, args)

   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/MySQLdb/cursors.py", line 179, in execute
 res = self._query(mogrified_query)
   

Re: [Django] #35369: MySQL .union().aggregate() raises Unknown Column

[Django]

#35369: MySQL .union().aggregate() raises Unknown Column
-+-
 Reporter:  DS/Charlie   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  union,aggregate,mysql  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by DS/Charlie:

Old description:

> ```
> class BugModel(models.Model):
> foo = models.CharField(max_length=255)
>
> class BugTestCase(TestCase):
> def test_bug(self):
> a = BugModel.objects.all()
> b = BugModel.objects.all()
>
> ab = a.union(b, all=False)
> """
> (
> SELECT `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> ) UNION (
> SELECT `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> )
> """
>
> ab.aggregate(max=Max("foo"))
> """
> SELECT MAX(`__col1`)
> FROM (
> (
> SELECT  `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> ) UNION (
> SELECT `bugapp_bugmodel`.`id` AS `col1`,
> `bugapp_bugmodel`.`foo` AS `col2`
> FROM `bugapp_bugmodel`
> )
> ) subquery
>

> Traceback (most recent call last):
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/django/db/backends/utils.py", line 89, in _execute
> return self.cursor.execute(sql, params)
>
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/django/db/backends/mysql/base.py", line 75, in execute
> return self.cursor.execute(query, args)
>
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/MySQLdb/cursors.py", line 179, in execute
> res = self._query(mogrified_query)
>   
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/MySQLdb/cursors.py", line 330, in _query
> db.query(q)
>   File "/private/tmp/djangobug/venv/lib/python3.12/site-
> packages/MySQLdb/connections.py", line 261, in query
> _mysql.connection.query(self, query)
> MySQLdb.OperationalError: (1054, "Unknown column '__col1' in
> 'field list'")
> """
> ```
>

> Django 4.2.11 and 5.0.4
> mysqlclient 2.2.4
>
> all in a clean virtualenv on python 3.12.2

New description:

 {{{

 class BugModel(models.Model):
 foo = models.CharField(max_length=255)

 class BugTestCase(TestCase):
 def test_bug(self):
 a = BugModel.objects.all()
 b = BugModel.objects.all()

 ab = a.union(b, all=False)
 """
 (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 ) UNION (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 )
 """

 ab.aggregate(max=Max("foo"))
 """
 SELECT MAX(`__col1`)
 FROM (
 (
 SELECT  `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 ) UNION (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 )
 ) subquery


 Traceback (most recent call last):
   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/django/db/backends/utils.py", line 89, in _execute
 return self.cursor.execute(sql, params)

   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/django/db/backends/mysql/base.py", line 75, in execute
 return self.cursor.execute(query, args)

   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/MySQLdb/cursors.py", line 179, in execute
 res = self._query(mogrified_query)
   

[Django] #35369: MySQL .union().aggregate() raises Unknown Column

[Django]

#35369: MySQL .union().aggregate() raises Unknown Column
-+-
   Reporter: |  Owner:  nobody
  DS/Charlie |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  5.0
  layer (models, ORM)|   Keywords:
   Severity:  Normal |  union,aggregate,mysql
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 ```
 class BugModel(models.Model):
 foo = models.CharField(max_length=255)

 class BugTestCase(TestCase):
 def test_bug(self):
 a = BugModel.objects.all()
 b = BugModel.objects.all()

 ab = a.union(b, all=False)
 """
 (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 ) UNION (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 )
 """

 ab.aggregate(max=Max("foo"))
 """
 SELECT MAX(`__col1`)
 FROM (
 (
 SELECT  `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 ) UNION (
 SELECT `bugapp_bugmodel`.`id` AS `col1`,
 `bugapp_bugmodel`.`foo` AS `col2`
 FROM `bugapp_bugmodel`
 )
 ) subquery


 Traceback (most recent call last):
   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/django/db/backends/utils.py", line 89, in _execute
 return self.cursor.execute(sql, params)

   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/django/db/backends/mysql/base.py", line 75, in execute
 return self.cursor.execute(query, args)

   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/MySQLdb/cursors.py", line 179, in execute
 res = self._query(mogrified_query)
   
   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/MySQLdb/cursors.py", line 330, in _query
 db.query(q)
   File "/private/tmp/djangobug/venv/lib/python3.12/site-
 packages/MySQLdb/connections.py", line 261, in query
 _mysql.connection.query(self, query)
 MySQLdb.OperationalError: (1054, "Unknown column '__col1' in
 'field list'")
 """
 ```


 Django 4.2.11 and 5.0.4
 mysqlclient 2.2.4

 all in a clean virtualenv on python 3.12.2
-- 
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/0107018ed2e60f1f-aef23ac6-5bbe-4940-8574-dee48f03ea36-00%40eu-central-1.amazonses.com.

Re: [Django] #35189: Accessibility issues with collapsed fieldsets in admin forms

[Django]

#35189: Accessibility issues with collapsed fieldsets in admin forms
-+-
 Reporter:  Thibaud Colas|Owner:  Marijke
 Type:   |  Luttekes
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  whcm, forced colors, screen|
  reader, forms, admin   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Sarah Boyce):

 * needs_better_patch:  0 => 1

Comment:

 I can see the accessibility team also has this in their review queue:
 https://github.com/orgs/django/projects/7, so hopefully you will receive
 another review 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/0107018ed2dbcdd6-9141e909-7673-4cfb-9c66-fd86a263f5cd-00%40eu-central-1.amazonses.com.

Re: [Django] #35359: Got `django.core.exceptions.FieldError` when adding GeneratedField

[Django]

#35359: Got `django.core.exceptions.FieldError` when adding GeneratedField
-+
 Reporter:  wd0517   |Owner:  Bhuvnesh
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  GeneratedField   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Bhuvnesh):

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

Comment:

 [https://github.com/django/django/pull/18068 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/0107018ed2c9c306-6e5cd1f3-1d84-45c8-b2cc-caedd3f5f3a8-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Improve documentation for the various date format settings

[Django]

#35306: Improve documentation for the various date format settings
-+-
 Reporter:  Richard  |Owner:  Lufafa
 Type:   |  Joshua
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:  Accepted
  DATE_FORMAT|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Rich):

 That works for me - thanks Lufafa!
-- 
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/0107018ed28950ee-a86839a5-e1de-4c47-bf8c-24f3975e2546-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Improve documentation for the various date format settings

[Django]

#35306: Improve documentation for the various date format settings
-+-
 Reporter:  Richard  |Owner:  Lufafa
 Type:   |  Joshua
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:  Accepted
  DATE_FORMAT|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Lufafa Joshua):

 Hey Richard, does this work for you
 [https://github.com/django/django/pull/18028 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/0107018ed277d8c1-90be764f-9d51-4199-a472-9a272862f941-00%40eu-central-1.amazonses.com.

Re: [Django] #35361: SafeMIMEText.set_payload() crash on Python 3.11.9

[Django]

#35361: SafeMIMEText.set_payload() crash on Python 3.11.9
-+-
 Reporter:  Sarah Boyce  |Owner:  Natalia
 |  Bidart
 Type:  Bug  |   Status:  closed
Component:  Core (Mail)  |  Version:  4.2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"1d85b416aa1382e7274e718c79b83dd050fb24ab" 1d85b416]:
 {{{#!CommitTicketReference repository=""
 revision="1d85b416aa1382e7274e718c79b83dd050fb24ab"
 [4.2.x] Refs #35361 -- Clarified release notes for 4.2.12.

 Backport of cd823778e66307b82469858cfd8d1aa75613b49a from main.
 }}}
-- 
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/0107018ed26d9118-f59f55f2-6c75-4fba-a59b-5adcb2c804f3-00%40eu-central-1.amazonses.com.

Re: [Django] #35336: Adding GeneratedField fails with ProgrammingError when using When on CharField

[Django]

#35336: Adding GeneratedField fails with ProgrammingError when using When on
CharField
-+-
 Reporter:  Adrian Garcia|Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  postgres,| Triage Stage:  Ready for
  generatedfield, contains   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"5d95a1c35ef1375a7badcb217c36c5974d1e57ee" 5d95a1c]:
 {{{#!CommitTicketReference repository=""
 revision="5d95a1c35ef1375a7badcb217c36c5974d1e57ee"
 [5.0.x] Refs #35194 -- Adjusted a generated field test to work on Postgres
 15.6+.

 Postgres >= 12.18, 13.14, 14.11, 15.6, 16.2 changed the way the
 immutability
 of generated and default expressions is detected in
 postgres/postgres@743ddaf.

 The adjusted test semantic is presereved by switching from __icontains to
 __contains as both make use of a `%` literal which requires proper
 escaping.

 Refs #35336.

 Thanks bcail for the report.

 Backport of 73b62a21265c4a417004d64d13a896469e2558f3 from main.
 }}}
-- 
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/0107018ed265d787-3335be85-617a-46ce-b820-16e8b883abc4-00%40eu-central-1.amazonses.com.

Re: [Django] #35194: Postgres 16.2 with _iexact leads to IndeterminateCollation

[Django]

#35194: Postgres 16.2 with _iexact leads to IndeterminateCollation
-+-
 Reporter:  Aldalen  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 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 Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"5d95a1c35ef1375a7badcb217c36c5974d1e57ee" 5d95a1c]:
 {{{#!CommitTicketReference repository=""
 revision="5d95a1c35ef1375a7badcb217c36c5974d1e57ee"
 [5.0.x] Refs #35194 -- Adjusted a generated field test to work on Postgres
 15.6+.

 Postgres >= 12.18, 13.14, 14.11, 15.6, 16.2 changed the way the
 immutability
 of generated and default expressions is detected in
 postgres/postgres@743ddaf.

 The adjusted test semantic is presereved by switching from __icontains to
 __contains as both make use of a `%` literal which requires proper
 escaping.

 Refs #35336.

 Thanks bcail for the report.

 Backport of 73b62a21265c4a417004d64d13a896469e2558f3 from main.
 }}}
-- 
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/0107018ed265d721-801aa4eb-94e2-4bb8-bc99-f12c9d027eaf-00%40eu-central-1.amazonses.com.

Re: [Django] #35361: SafeMIMEText.set_payload() crash on Python 3.11.9

[Django]

#35361: SafeMIMEText.set_payload() crash on Python 3.11.9
-+-
 Reporter:  Sarah Boyce  |Owner:  Natalia
 |  Bidart
 Type:  Bug  |   Status:  closed
Component:  Core (Mail)  |  Version:  4.2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"a1baaddb67a59f32db9e10f44ac76e9835ca4e84" a1baaddb]:
 {{{#!CommitTicketReference repository=""
 revision="a1baaddb67a59f32db9e10f44ac76e9835ca4e84"
 [5.0.x] Refs #35361 -- Clarified release notes for 4.2.12 and 5.0.5.

 Backport of cd823778e66307b82469858cfd8d1aa75613b49a from main.
 }}}
-- 
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/0107018ed265d7c0-f21be9d8-dceb-469c-be2c-94ab0c443c4d-00%40eu-central-1.amazonses.com.

Re: [Django] #35361: SafeMIMEText.set_payload() crash on Python 3.11.9

[Django]

#35361: SafeMIMEText.set_payload() crash on Python 3.11.9
-+-
 Reporter:  Sarah Boyce  |Owner:  Natalia
 |  Bidart
 Type:  Bug  |   Status:  closed
Component:  Core (Mail)  |  Version:  4.2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"cd823778e66307b82469858cfd8d1aa75613b49a" cd823778]:
 {{{#!CommitTicketReference repository=""
 revision="cd823778e66307b82469858cfd8d1aa75613b49a"
 Refs #35361 -- Clarified release notes for 4.2.12 and 5.0.5.
 }}}
-- 
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/0107018ed252b714-068b2cb0-0ce1-47db-8ce5-a9a4d3f71eb7-00%40eu-central-1.amazonses.com.

Re: [Django] #35359: Got `django.core.exceptions.FieldError` when adding GeneratedField

[Django]

#35359: Got `django.core.exceptions.FieldError` when adding GeneratedField
-+
 Reporter:  wd0517   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  GeneratedField   | 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):

 > Hm can't fks depend on these though because the constraints for those
 are also grouped together last. 樂

 Right. Since `GeneratedField` cannot be foreign keys though it should
 still allow for the following grouping of fields?

 `non_fk_non_generated_field | generated_fields | fk_fields`
-- 
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/0107018ed2295305-3a0ab4c1-eb32-461b-a57c-2899dc535bdf-00%40eu-central-1.amazonses.com.

Re: [Django] #35364: AdminEmailHandler wastes work when ADMINS isn’t set

[Django]

#35364: AdminEmailHandler wastes work when ADMINS isn’t set
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 Type:   |  Johnson
  Cleanup/optimization   |   Status:  closed
Component:  Error reporting  |  Version:  dev
 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:"50a702f3fd87e271945aa5e88ae8a39d7a2149fd" 50a702f]:
 {{{#!CommitTicketReference repository=""
 revision="50a702f3fd87e271945aa5e88ae8a39d7a2149fd"
 Fixed #35364 -- Stopped AdminEmailHandler rendering email unnecessarily.
 }}}
-- 
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/0107018ed17470e2-deeaae47-1b3b-4a51-a727-7cc0d8ac4e36-00%40eu-central-1.amazonses.com.

Re: [Django] #35364: AdminEmailHandler wastes work when ADMINS isn’t set

[Django]

#35364: AdminEmailHandler wastes work when ADMINS isn’t set
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 Type:   |  Johnson
  Cleanup/optimization   |   Status:  assigned
Component:  Error reporting  |  Version:  dev
 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
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"b0f2289426d2af0d3f31e50bd8d5e60a49d62710" b0f2289]:
 {{{#!CommitTicketReference repository=""
 revision="b0f2289426d2af0d3f31e50bd8d5e60a49d62710"
 Refs #35364 -- Tested AdminEmailHandler with empty ADMINS.
 }}}
-- 
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/0107018ed17470a7-fda13f76-da03-48bd-8a40-890b00d6e974-00%40eu-central-1.amazonses.com.

Re: [Django] #35336: Adding GeneratedField fails with ProgrammingError when using When on CharField

[Django]

#35336: Adding GeneratedField fails with ProgrammingError when using When on
CharField
-+-
 Reporter:  Adrian Garcia|Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  postgres,| Triage Stage:  Ready for
  generatedfield, contains   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"73b62a21265c4a417004d64d13a896469e2558f3" 73b62a21]:
 {{{#!CommitTicketReference repository=""
 revision="73b62a21265c4a417004d64d13a896469e2558f3"
 Refs #35194 -- Adjusted a generated field test to work on Postgres 15.6+.

 Postgres >= 12.18, 13.14, 14.11, 15.6, 16.2 changed the way the
 immutability
 of generated and default expressions is detected in
 postgres/postgres@743ddaf.

 The adjusted test semantic is presereved by switching from __icontains to
 __contains as both make use of a `%` literal which requires proper
 escaping.

 Refs #35336.

 Thanks bcail for the report.
 }}}
-- 
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/0107018ed16743c4-e8052341-2e91-4e2f-8f85-0da94204f26d-00%40eu-central-1.amazonses.com.

Re: [Django] #35194: Postgres 16.2 with _iexact leads to IndeterminateCollation

[Django]

#35194: Postgres 16.2 with _iexact leads to IndeterminateCollation
-+-
 Reporter:  Aldalen  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 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 Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"73b62a21265c4a417004d64d13a896469e2558f3" 73b62a21]:
 {{{#!CommitTicketReference repository=""
 revision="73b62a21265c4a417004d64d13a896469e2558f3"
 Refs #35194 -- Adjusted a generated field test to work on Postgres 15.6+.

 Postgres >= 12.18, 13.14, 14.11, 15.6, 16.2 changed the way the
 immutability
 of generated and default expressions is detected in
 postgres/postgres@743ddaf.

 The adjusted test semantic is presereved by switching from __icontains to
 __contains as both make use of a `%` literal which requires proper
 escaping.

 Refs #35336.

 Thanks bcail for the report.
 }}}
-- 
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/0107018ed1674368-b343eedb-9bca-460e-9cb4-a8de085638aa-00%40eu-central-1.amazonses.com.

Re: [Django] #35194: Postgres 16.2 with _iexact leads to IndeterminateCollation

[Django]

#35194: Postgres 16.2 with _iexact leads to IndeterminateCollation
-+-
 Reporter:  Aldalen  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 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 Sarah Boyce):

 * resolution:  needsinfo =>
 * 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/0107018ed164bba0-6cde75e3-abfe-4116-9cb8-16a581d94993-00%40eu-central-1.amazonses.com.

Re: [Django] #22997: Migration fails when removing explicit primary key (Postgres)

[Django]

#22997: Migration fails when removing explicit primary key (Postgres)
-+
 Reporter:  a.lloyd.flanagan@…   |Owner:  bcail
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  migrate primary_key  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Bhuvnesh):

 * 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/0107018ed13f7052-e53e627a-3b35-4207-a064-34f99430af21-00%40eu-central-1.amazonses.com.