Opened 4 months ago

Last modified 4 months ago

#35608 closed Bug

Regression: many-to-many fields are not being correctly persisted to db from the admin — at Version 1

Reported by: Adrian Capitanu Owned by:
Component: contrib.admin Version: 5.1
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Adrian Capitanu)

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

Repro rate:

  • inconsistent
  • maybe related to connection pooling?

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

Change History (1)

comment:1 by Adrian Capitanu, 4 months ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.
Back to Top