id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
36262	GeneratedField.db_persist defaults to None but is required to be set as either True or False	Jason Cameron	Jason Cameron	"**Description**:
`GeneratedField.db_persist` attribute is set to `db_persist=None`, which implies that the value can be `None`. However, just 4 lines lower in the code, it is required to be either `True` or `False`. This inconsistency leads a developer to believe that it can be left blank but it cannot.

**Steps to Reproduce**:
1. Create a model using `GeneratedField` with `db_persist=None` or `db_persist` not set.
2. Run the server or execute a command that requires the field validation.
3. Observe that the code expects the value to be `True` or `False` despite it being set to `None`.

**Expected Behavior**:
The `db_persist` attribute should consistently accept `None` throughout the code if it is defined as `None=True`.

**Actual Behavior**:
The code expects `db_persist` to be either `True` or `False` and does not handle the `None` value appropriately.

Would fix https://github.com/typeddjango/django-stubs/pull/2568"	Cleanup/optimization	assigned	Database layer (models, ORM)	dev	Normal			Jason Cameron	Accepted	1	0	0	1	1	0