Re: [Django] #35422: Migration crash when renaming a field referenced in GeneratedField.expression

[Django]

#35422: Migration crash when renaming a field referenced in
GeneratedField.expression
-+-
 Reporter:  Sarah Boyce  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  5.0
 Severity:  Release blocker  |   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/0107018f3d1c678f-d5c268c8-3b3e-4d7e-bc3b-19ebed1caf2a-00%40eu-central-1.amazonses.com.

[Django] #35424: Migration autodetector fails when order_with_respect_to is removed, but an _order field remains

[Django]

#35424: Migration autodetector fails when order_with_respect_to is removed, but 
an
_order field remains
--+
   Reporter:  stuarta0|  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Migrations  |Version:  4.2
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  0   |
--+
 We have a project with a large number of migrations that began failing
 during migrate/makemigrations due to order_with_respect_to having been
 removed, and an explicit _order field added. The historic migration
 contains this operation:

 {{{
 migrations.AlterOrderWithRespectTo(
 name='choice',
 order_with_respect_to=None,
 ),
 }}}

 This causes an issue with the code introduced in commit
 
https://github.com/django/django/commit/aa4acc164d1247c0de515c959f7b09648b57dc42
 which was subsequently "fixed" in
 https://code.djangoproject.com/ticket/33449 but remains failing in the
 case described above.

 A minimal reproducible case has been created here:
 https://github.com/stuarta0/django-order-with-respect-to based on the
 django docs polls app.

 A possible solution may be to fall back to field_name if
 order_with_respect_to is either missing, or present with None (which is
 what occurs above):

 {{{
 def get_field(self, field_name):
 if field_name == "_order":
 field_name = self.options.get("order_with_respect_to") or
 field_name
 return self.fields[field_name]
 }}}
-- 
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/0107018f3d1648cb-d7615771-8955-4d42-aaa0-5444c7b76de3-00%40eu-central-1.amazonses.com.

Re: [Django] #8576: Multiple AutoFields in a model

[Django]

#8576: Multiple AutoFields in a model
-+-
 Reporter:  honeyman |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multiple autofield   | Triage Stage:  Design
 |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Csirmaz Bendegúz):

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

Comment:

 [https://code.djangoproject.com/ticket/373]
 I'm looking to implement composite primary keys like this:

 {{{
 class Tenant(models.Model):
 pass


 class User(models.Model):
 tenant = models.ForeignKey(Tenant, on_delete=models.CASCADE)
 id = models.SmallAutoField()

 class Meta:
 primary_key = ("tenant_id", "id")
 }}}

 In order to encourage using surrogate keys in composite primary keys, it
 would make a lot of sense to allow non-primary key auto fields.

 We have the following options:
 1. Remove the limitation for databases that support non-primary auto
 fields altogether. We could allow non-primary key auto fields for
 PostgreSQL, for example.
 2. Refactor auto fields so that they are either primary keys OR part of a
 composite primary key. This addresses my use case, but not the others.
 3. Don't use auto fields in composite primary keys. We need an alternative
 in this case.
-- 
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/0107018f3c36f113-aae666d3-424b-448e-ae40-4c7482b4a846-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:  closed
Component:  Migrations   |  Version:  5.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  GeneratedField   | 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 Natalia <124304+nessita@…>):

 In [changeset:"24f54c3b09ab4f19bfc11c5d7ba80985ed870103" 24f54c3]:
 {{{#!CommitTicketReference repository=""
 revision="24f54c3b09ab4f19bfc11c5d7ba80985ed870103"
 [5.0.x] Fixed #35359 -- Fixed migration operations ordering when adding
 fields referenced by GeneratedField.expression.

 Thank you to Simon Charette for the review.

 Backport of 9aeb38c296c69532c7e64b5e3d706a5eb17b3f12 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/0107018f3c0019c9-a7807879-60c7-4122-922c-83aac3ea8e82-00%40eu-central-1.amazonses.com.

Re: [Django] #34007: Single-field conditional UniqueContraint validation errors are classified as non-field-errors

[Django]

#34007: Single-field conditional UniqueContraint validation errors are 
classified
as non-field-errors
-+-
 Reporter:  David Sanders|Owner:  David
 Type:   |  Sanders
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Natalia <124304+nessita@…>):

 In [changeset:"fa202d5cb1f16b9bbfd9da72eb03125fabc34bb8" fa202d5c]:
 {{{#!CommitTicketReference repository=""
 revision="fa202d5cb1f16b9bbfd9da72eb03125fabc34bb8"
 [5.0.x] Refs #34007, Refs #35359 -- Added Q.referenced_based_fields
 property.

 Thank you to Mariusz Felisiak and Natalia Bidart for the reviews.

 Backport of 97d48cd3c6f409584b5cc19fbddfca917bae78fd 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/0107018f3c001976-d0ed4503-e9d6-4f25-86ae-7691f442989f-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:  closed
Component:  Migrations   |  Version:  5.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  GeneratedField   | 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 Natalia <124304+nessita@…>):

 In [changeset:"fa202d5cb1f16b9bbfd9da72eb03125fabc34bb8" fa202d5c]:
 {{{#!CommitTicketReference repository=""
 revision="fa202d5cb1f16b9bbfd9da72eb03125fabc34bb8"
 [5.0.x] Refs #34007, Refs #35359 -- Added Q.referenced_based_fields
 property.

 Thank you to Mariusz Felisiak and Natalia Bidart for the reviews.

 Backport of 97d48cd3c6f409584b5cc19fbddfca917bae78fd 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/0107018f3c00197b-45df006e-56a4-4134-a030-c5b9c3c0d717-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:  closed
Component:  Migrations   |  Version:  5.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  GeneratedField   | 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 Natalia Bidart):

 * 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/0107018f3be82708-6c96808b-6fad-47bb-bdee-6d7294c017a3-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:  closed
Component:  Migrations   |  Version:  5.0
 Severity:  Release blocker  |   Resolution:  fixed
 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 nessita <124304+nessita@…>):

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

Comment:

 In [changeset:"9aeb38c296c69532c7e64b5e3d706a5eb17b3f12" 9aeb38c2]:
 {{{#!CommitTicketReference repository=""
 revision="9aeb38c296c69532c7e64b5e3d706a5eb17b3f12"
 Fixed #35359 -- Fixed migration operations ordering when adding fields
 referenced by GeneratedField.expression.

 Thank you to Simon Charette for the 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/0107018f3be7d12c-fcaca1e9-dee2-4348-a63c-1c786a82edc4-00%40eu-central-1.amazonses.com.

Re: [Django] #35422: Migration crash when renaming a field referenced in GeneratedField.expression

[Django]

#35422: Migration crash when renaming a field referenced in
GeneratedField.expression
-+-
 Reporter:  Sarah Boyce  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * has_patch:  0 => 1

Comment:

 [https://github.com/django/django/pull/18122 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/0107018f3a9e2607-0f03340d-d21f-470d-bfb5-6e9071b4f343-00%40eu-central-1.amazonses.com.

Re: [Django] #35422: Migration crash when renaming a field referenced in GeneratedField.expression

[Django]

#35422: Migration crash when renaming a field referenced in
GeneratedField.expression
-+-
 Reporter:  Sarah Boyce  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  5.0
 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 Mariusz Felisiak):

 * owner:  nobody => Mariusz Felisiak
 * 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/0107018f3a82f2c3-9fa7ec1b-1cdd-4d10-8656-6e1234d69c85-00%40eu-central-1.amazonses.com.

Re: [Django] #35422: Migration crash when renaming a field referenced in GeneratedField.expression (was: Migration crash when renaming a field referenced in GeneratedField.expression on SQLite)

[Django]

#35422: Migration crash when renaming a field referenced in
GeneratedField.expression
-+
 Reporter:  Sarah Boyce  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  5.0
 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):

 * summary:
 Migration crash when renaming a field referenced in
 GeneratedField.expression on SQLite
 =>
 Migration crash when renaming a field referenced in
 GeneratedField.expression

Comment:

 > In other words, if we can't generate the SQL for the old field anymore
 but we can for the new one then it was certainly changed and the same lack
 of alteration support limitation applies.

 Makes sense! Agree that I found this on SQLite is irrelevant
-- 
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/0107018f3a4f5fc9-65adc2e8-deee-4c15-9e05-0e4f2e07c114-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
-+
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"97d48cd3c6f409584b5cc19fbddfca917bae78fd" 97d48cd]:
 {{{#!CommitTicketReference repository=""
 revision="97d48cd3c6f409584b5cc19fbddfca917bae78fd"
 Refs #34007, Refs #35359 -- Added Q.referenced_based_fields property.

 Thank you to Mariusz Felisiak and Natalia Bidart for the reviews.
 }}}
-- 
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/0107018f3a448098-f15608d1-c1ff-4091-853e-0f75a82ee137-00%40eu-central-1.amazonses.com.

Re: [Django] #34007: Single-field conditional UniqueContraint validation errors are classified as non-field-errors

[Django]

#34007: Single-field conditional UniqueContraint validation errors are 
classified
as non-field-errors
-+-
 Reporter:  David Sanders|Owner:  David
 Type:   |  Sanders
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"97d48cd3c6f409584b5cc19fbddfca917bae78fd" 97d48cd]:
 {{{#!CommitTicketReference repository=""
 revision="97d48cd3c6f409584b5cc19fbddfca917bae78fd"
 Refs #34007, Refs #35359 -- Added Q.referenced_based_fields property.

 Thank you to Mariusz Felisiak and Natalia Bidart for the reviews.
 }}}
-- 
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/0107018f3a448072-2ee84070-ef07-4612-a0f0-2cee9e379da0-00%40eu-central-1.amazonses.com.

Re: [Django] #35422: Migration crash when renaming a field referenced in GeneratedField.expression on SQLite

[Django]

#35422: Migration crash when renaming a field referenced in
GeneratedField.expression on SQLite
-+
 Reporter:  Sarah Boyce  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  5.0
 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 Simon Charette):

 I don't think the problem is specific to SQLite.

 The non-invasive back portable solution I can think of is for `FieldError`
 to be caught and also result in a `ValueError` pointing out that the
 generated field must be removed first.
-- 
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/0107018f3a23b309-1b0a8ab0-8fdc-474c-95d8-6d517b0bbdf7-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
-+-
Changes (by Natalia Bidart):

 * cc: Thibaud Colas, Tom Carrick, Sarah Abderemane (added)
 * stage:  Unreviewed => Accepted
 * type:  New feature => Cleanup/optimization

Comment:

 Hello RenDelaCruz, thank you for your interest in making Django better.

 I can relate to your report, and I can see value in a small help text
 below the search box. I'm tentatively accepting to see how this would look
 like in the UI, are you available to propose a PR? We would love to count
 on your contribution for this!

 We should definitely consider the accessibility aspects of this, but IMHO
 as long as the adding is equivalent to form fields help text, this should
 comply with all the accessibility requirements.
-- 
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/0107018f3a1e6852-ccb56c72-40ea-4c1b-a605-ff3b8154385e-00%40eu-central-1.amazonses.com.

Re: [Django] #35422: Migration crash when renaming a field referenced in GeneratedField.expression on SQLite

[Django]

#35422: Migration crash when renaming a field referenced in
GeneratedField.expression on SQLite
-+
 Reporter:  Sarah Boyce  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  5.0
 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 Natalia Bidart):

 * cc: David Sanders, Bhuvnesh (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/0107018f3a17799b-5479eaa6-5bae-4709-b667-32d5b9522d21-00%40eu-central-1.amazonses.com.

Re: [Django] #35422: Migration crash when renaming a field referenced in GeneratedField.expression on SQLite

[Django]

#35422: Migration crash when renaming a field referenced in
GeneratedField.expression on SQLite
-+
 Reporter:  Sarah Boyce  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  5.0
 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 Natalia Bidart):

 * cc: Simon Charette, Mariusz Felisiak, Lily Foote (added)
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted

Comment:

 Thank you Sarah, I reproduced and confirmed that this is not a dupe of
 #35359 (or at least the fix for that ticket is not fixing this issue).

 This is a release blocker for 5.0 given that `GeneratedField` was added in
 that Django version. I also reproduced in
 f333e3513e8bdf5ffeb6eeb63021c230082e6f95.
-- 
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/0107018f3a145501-15fdaa4f-dca0-4705-ba85-ccca1524d545-00%40eu-central-1.amazonses.com.

Re: [Django] #32519: Add support for using key and path transforms in update() for JSONFields.

[Django]

#32519: Add support for using key and path transforms in update() for 
JSONFields.
-+-
 Reporter:  Baptiste Mispelon|Owner:  Shafiya
 |  Adzhani
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (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 Shafiya Adzhani):

 * owner:  Kamil Turek => Shafiya Adzhani

Comment:

 I will work on this ticket during GSoC. Hopefully we will land these new
 features 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/0107018f39e6b965-c5f0f9cb-afc2-4d0c-8efd-6fe847687110-00%40eu-central-1.amazonses.com.

[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: |  Owner:  nobody
  RenDelaCruz|
   Type:  New| Status:  new
  feature|
  Component: |Version:  5.0
  contrib.admin  |   Keywords:  admin,
   Severity:  Normal |  search_fields, change_list, search,
   Triage Stage: |  ui
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  1  |
-+-
 In any Django Admin change_list pages, when including a `search_fields`
 attribute, the search bar does not indicate which fields are searchable.
 This can easily be confused with attributes on the sidebar `list_filter`.

 Maybe something like a greyed-out caption indicating the model fields
 included in `search_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/0107018f39e45269-077a2fc6-fadf-435b-8b2a-afb4461ab905-00%40eu-central-1.amazonses.com.

Re: [Django] #35418: ValueError: site must subclass AdminSite

[Django]

#35418: ValueError: site must subclass AdminSite
--+
 Reporter:  Lily Foote|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  5.0
 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 Sarah Boyce):

 * component:  Uncategorized => Utilities
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Cleanup/optimization

Comment:

 Hey Lily, thank you for creating this ticket and summarizing the current
 situation, including the update of the PyPy bug link.
 This is a tricky one - tentatively accepting to track further
 investigation of a workaround. A fix in CPython or PyPy sounds preferable
 and if these start progressing, this will likely be closed as a wontfix.
 But discussed with Natalia, and we're happy to look at a PR proposing the
 mentioned workaround (a test would also be needed, which from comments in
 #28358 that may be challenging).
-- 
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/0107018f39d6a163-3568cbd2-04eb-4778-acdb-368b2e2d6632-00%40eu-central-1.amazonses.com.

Re: [Django] #35415: Adding content_type to StreamingHttpResponse on Linux causes memory error after streaming around 1GB-2GB of data.

[Django]

#35415: Adding content_type to StreamingHttpResponse on Linux causes memory 
error
after streaming around 1GB-2GB of data.
---+--
 Reporter:  LouisB12345|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  5.0
 Severity:  Normal |   Resolution:  invalid
 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 Natalia Bidart):

 * resolution:  needsinfo => invalid

Comment:

 Hello LouisB12345! Thank you for your report. As Sarah mentioned, the best
 course of action at this point is to reach out to the community in the
 [https://forum.djangoproject.com/c/internals/async/8 Django Forum (async
 category)] to get help debugging your view, since we are not able to
 reproduce. See below for the full details of the reproducer that I setup
 locally, streaming a 3.3G iso image, without getting any memory usage
 increase nor memory error.

 Since the goal of this issue tracker is to track issues about Django
 itself, and your issue seems, at first, to be located in your custom code,
 I'll be closing this ticket as invalid following the
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#closing-tickets ticket triaging process]. If, after debugging,
 you find out that this is indeed a bug in Django, please re-open with the
 specific details and please be sure to include a small but complete Django
 project to reproduce or a failing test case.

 The reproducer I used looks as follows:
 * A local Django project (`projectfromrepo`) with an app for this ticket
 (`ticket_35415`)
 * `uvicorn` installed and serving Django with `python -Wall -m uvicorn
 projectfromrepo.asgi:application --reload`
 * A views.py with this (slightly simplified) content:
 {{{#!python
 import aiofiles
 import logging
 import os
 import threading

 from django.http import StreamingHttpResponse


 logger = logging.getLogger(__name__)


 def debug(msg):
 logger.info(msg)
 print(msg)


 def file_download(request):
 file_name = "/home/nessita/debian-live-12.2.0-amd64-kde.iso"
 assert os.path.exists(file_name)
 debug(f"Requested {file_name} which stats {os.stat(file_name)=}.")
 response = StreamingHttpResponse(
 file_data(file_name), content_type="application/octet-stream"
 )
 response["Content-Disposition"] = f'attachment;
 filename="{file_name}"'
 return response


 async def file_data(file_path, chunk_size=65536):
 debug(f"Current threads are {threading.active_count()} opening file
 {file_path}.")
 async with aiofiles.open(file_path, mode="rb") as f:
 teller = 0
 while chunk := await f.read(chunk_size):
 teller += 1
 if teller % 1000 == 0:
 debug(
 f"Current threads are {threading.active_count()}
 yielding chunk nr.{teller}."
 )
 yield chunk
 }}}
 * Included the following in the main urls.py `path("streaming/",
 ticket_35415.views.file_download)`
 * Visiting http://localhost:8000/streaming/ works without any issues and
 the downloaded file matches the hash of the source file. What's printed in
 the terminal:
 {{{
 (djangodev) [nessita@socrates projectfromrepo]$ python -Wall -m uvicorn
 projectfromrepo.asgi:application --reload
 INFO: Will watch for changes in these directories:
 ['/home/nessita/fellowship/projectfromrepo']
 INFO: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
 INFO: Started reloader process [435237] using StatReload
 Requested /home/nessita/debian-live-12.2.0-amd64-kde.iso which stats
 os.stat(file_name)=os.stat_result(st_mode=33188, st_ino=8093957,
 st_dev=66306, st_nlink=1, st_uid=1001, st_gid=1001, st_size=3492741120,
 st_atime=1698110826, st_mtime=1698112190, st_ctime=1698112191).
 Current threads are 2 opening file /home/nessita/debian-
 live-12.2.0-amd64-kde.iso.
 Current threads are 4 yielding chunk nr.1000.
 Current threads are 4 yielding chunk nr.2000.
 Current threads are 4 yielding chunk nr.3000.
 Current threads are 4 yielding chunk nr.4000.
 Current threads are 4 yielding chunk nr.5000.
 Current threads are 4 yielding chunk nr.6000.
 Current threads are 4 yielding chunk nr.7000.
 Current threads are 4 yielding chunk nr.8000.
 Current threads are 4 yielding chunk nr.9000.
 Current threads are 4 yielding chunk nr.1.
 Current threads are 4 yielding chunk nr.11000.
 Current threads are 4 yielding chunk nr.12000.
 Current threads are 4 yielding chunk nr.13000.
 Current threads are 4 yielding chunk nr.14000.
 Current threads are 4

[Django] #35422: Migration crash when renaming a field referenced in GeneratedField.expression on SQLite

[Django]

#35422: Migration crash when renaming a field referenced in
GeneratedField.expression on SQLite
---+
   Reporter:  Sarah Boyce  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Migrations   |Version:  5.0
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 Given a model (migrated) on SQLite
 {{{
 class Foo(models.Model):
 name = models.CharField(max_length=10)
 lower_name = models.GeneratedField(
 expression=Lower("name"),
 output_field=models.CharField(max_length=10),
 db_persist=True,
 )
 }}}
 when you update to
 {{{
 class Foo(models.Model):
 surname = models.CharField(max_length=10)
 lower_name = models.GeneratedField(
 expression=Lower("surname"),
 output_field=models.CharField(max_length=10),
 db_persist=True,
 )
 }}}
 and makemigrations, you then get asked `Was foo.name renamed to
 foo.surname (a CharField)? [y/N]` and say `y` (because it was)
 You then get a crash when migrating:


 {{{
 Operations to perform:
   Apply all migrations: app3
 Running migrations:
   Applying
 app3.0005_rename_name_foo_surname_alter_foo_lower_name...Traceback (most
 recent call last):
   File "path_to_project\mysite\manage.py", line 22, in 
 main()
   File "path_to_project\mysite\manage.py", line 18, in main
 execute_from_command_line(sys.argv)
   File "path_to_project\venv\Lib\site-
 packages\django\core\management\__init__.py", line 442, in
 execute_from_command_line
 utility.execute()
   File "path_to_project\venv\Lib\site-
 packages\django\core\management\__init__.py", line 436, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "path_to_project\venv\Lib\site-
 packages\django\core\management\base.py", line 413, in run_from_argv
 self.execute(*args, **cmd_options)
   File "path_to_project\venv\Lib\site-
 packages\django\core\management\base.py", line 459, in execute
 output = self.handle(*args, **options)
  ^
   File "path_to_project\venv\Lib\site-
 packages\django\core\management\base.py", line 107, in wrapper
 res = handle_func(*args, **kwargs)
   
   File "path_to_project\venv\Lib\site-
 packages\django\core\management\commands\migrate.py", line 356, in handle
 post_migrate_state = executor.migrate(
  ^
   File "path_to_project\venv\Lib\site-
 packages\django\db\migrations\executor.py", line 135, in migrate
 state = self._migrate_all_forwards(
 ^^^
   File "path_to_project\venv\Lib\site-
 packages\django\db\migrations\executor.py", line 167, in
 _migrate_all_forwards
 state = self.apply_migration(
 ^
   File "path_to_project\venv\Lib\site-
 packages\django\db\migrations\executor.py", line 255, in apply_migration
 state = migration.apply(state, schema_editor)
 ^
   File "path_to_project\venv\Lib\site-
 packages\django\db\migrations\migration.py", line 132, in apply
 operation.database_forwards(
   File "path_to_project\venv\Lib\site-
 packages\django\db\migrations\operations\fields.py", line 241, in
 database_forwards
 schema_editor.alter_field(from_model, from_field, to_field)
   File "path_to_project\venv\Lib\site-
 packages\django\db\backends\base\schema.py", line 875, in alter_field
 or old_field.generated_sql(self.connection)

   File "path_to_project\venv\Lib\site-
 packages\django\db\models\fields\generated.py", line 58, in generated_sql
 resolved_expression = self.expression.resolve_expression(
   ^^^
   File "path_to_project\venv\Lib\site-
 packages\django\db\models\expressions.py", line 1052, in
 resolve_expression
 c.source_expressions[pos] = arg.resolve_expression(
 ^^^
   File "path_to_project\venv\Lib\site-
 packages\django\db\models\expressions.py", line 874, in resolve_expression
 return query.resolve_ref(self.name, allow_joins, reuse, summarize)
^^^
   File "path_to_project\venv\Lib\site-
 packages\django\db\models\sql\query.py", line 2010, in resolve_ref
 join_info = self.setup_joins(
 ^
   File "path_to_project\venv\Lib\site-
 packages\django\db\models\sql\query.py", line 1863, in setup_joins
 path, final_field, targe

Re: [Django] #35420: Add support for RSS stylesheets

[Django]

#35420: Add support for RSS stylesheets
-+-
 Reporter:  Baptiste Mispelon|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.syndication  |  Version:  5.0
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  rss, stylesheet  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Baptiste Mispelon):

 Hi,

 Sorry my mistake. I had searched on trac for an existing ticket but not
 well enough apparently (I think i just did a keyword search on "rss" in
 the summary).

 This ticket is an exact duplicate, and my PR is even really similar to the
 14 year old patch that was already attached 😅
-- 
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/0107018f391a1613-fd606e78-8d18-4a88-bfbd-cd20944965b3-00%40eu-central-1.amazonses.com.

Re: [Django] #32519: Add support for using key and path transforms in update() for JSONFields.

[Django]

#32519: Add support for using key and path transforms in update() for 
JSONFields.
-+-
 Reporter:  Baptiste Mispelon|Owner:  Kamil
 |  Turek
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (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 John Speno):

 * cc: John Speno (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/0107018f38d216f4-c37baf39-3e90-4afe-9919-6cde3c8b4716-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:  Yuval
 |  Adam
 Type:  New feature  |   Status:  new
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:  1
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Sarah Boyce):

 #35420 possible duplicate, with patch:
 https://github.com/django/django/pull/18120
-- 
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/0107018f38ab0250-9b55fe74-516a-48d4-89a4-4294c9c79599-00%40eu-central-1.amazonses.com.

Re: [Django] #35420: Add support for RSS stylesheets

[Django]

#35420: Add support for RSS stylesheets
-+-
 Reporter:  Baptiste Mispelon|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.syndication  |  Version:  5.0
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  rss, stylesheet  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

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

Comment:

 Hi Baptiste, I am not very knowledgeable in RSS feeds, but this feels
 related to #12978 and certainly the "motivation" behind it feels very
 similar.
 I'm going to mark this as a duplicate of #12978 but if you disagree,
 please let me know 👍
-- 
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/0107018f38aa1cd3-e91927c9-2941-479f-b3fb-d7fa66460f66-00%40eu-central-1.amazonses.com.

Re: [Django] #35384: Assigning a file without a name property to a FileField results in file getting discarded silently

[Django]

#35384: Assigning a file without a name property to a FileField results in file
getting discarded silently
-+-
 Reporter:  john-parton  |Owner:  Jonny
 |  Park
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by 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/0107018f389495b7-ccebb078-c598-4d80-9743-b7335e594ade-00%40eu-central-1.amazonses.com.

Re: [Django] #35417: RequestContext.new creates a context that cannot be flattened

[Django]

#35417: RequestContext.new creates a context that cannot be flattened
-+
 Reporter:  Lily Foote   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  5.0
 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 Sarah Boyce):

 * component:  Uncategorized => Template system

-- 
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/0107018f384dfab3-6b768a71-65ba-4b19-ab85-998c2cf651bd-00%40eu-central-1.amazonses.com.

Re: [Django] #35417: RequestContext.new creates a context that cannot be flattened

[Django]

#35417: RequestContext.new creates a context that cannot be flattened
---+
 Reporter:  Lily Foote |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  5.0
 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 Sarah Boyce):

 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Bug

Comment:

 Replicated (thank you for the test case) and also confirmed `Context` and
 `RenderContext`, 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/0107018f384a6de5-fa6eb655-62bb-4b58-a203-f886e7b733c9-00%40eu-central-1.amazonses.com.

Re: [Django] #29280: Add a database OPTIONS to specify the transaction mode one SQLite.

[Django]

#29280: Add a database OPTIONS to specify the transaction mode one SQLite.
-+-
 Reporter:  Ove Kåven|Owner:  Anže
 |  Pečar
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  sqlite, databases| 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:"9d5c02446e5947fbeb74dda1b6b246fd8268009d" 9d5c0244]:
 {{{#!CommitTicketReference repository=""
 revision="9d5c02446e5947fbeb74dda1b6b246fd8268009d"
 Refs #29280 -- Moved release note about transaction_mode to "Database
 backends" section.
 }}}
-- 
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/0107018f382c5ef6-f3de2531-def8-42a9-b0fa-501b7d66c401-00%40eu-central-1.amazonses.com.