#35608: Regression: many-to-many fields are not being correctly persisted to db
from the admin
----------------------------+-----------------------------------------
Reporter: captain828 | Type: Bug
Status: new | Component: contrib.admin
Version: 5.1 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+-----------------------------------------
**Prerequisites:**
- database: postgres16
- settings.py file that points to it
- have new connection pooling configured
- have a model that has a m2m field
- register that model to admin
- create a couple of instances to use in the m2m relationship
**Steps to repro:**
1. via admin, on a model with an m2m field, create a new model instance
with no m2m relationships and save
2. edit the same instance, adding extra m2m relationships and save
3. re-open the same instance and observe m2m field
**Expected result:**
The m2m field should have the options selected at (2) if the save was
successful.
**Current result:**
The m2m field does not have some or all the options selected at (2),
despite the save being successful.
**Affected Versions:** 5.1b1
**Working Versions:** 5.0.7
--
Ticket URL: <https://code.djangoproject.com/ticket/35608>
Django <https://code.djangoproject.com/>
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/01070190bcc79c11-cfd1d188-5e17-44c9-a914-747d1f7155ea-000000%40eu-central-1.amazonses.com.
