﻿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
35815	System check for default database values with expressions prohibits non-expressions	Tim Graham	Tim Graham	"Since its introduction in Django 5.0, [https://github.com/django/django/blob/c334c1a8ff4579cdb1dd77cce8da747070ac9fc4/django/db/models/fields/__init__.py#L411-L420 the fields.E011 system check] for database backends that have `DatabaseFeatures.supports_expression_defaults = False` [https://github.com/django/django/blob/c334c1a8ff4579cdb1dd77cce8da747070ac9fc4/django/db/models/fields/__init__.py#L393-L398 requires literal defaults to be wrapped in Value].

There are a number of test models that have [https://github.com/django/django/blob/c334c1a8ff4579cdb1dd77cce8da747070ac9fc4/tests/field_defaults/models.py#L46-L47 int, float] and [https://github.com/django/django/blob/c334c1a8ff4579cdb1dd77cce8da747070ac9fc4/tests/field_defaults/models.py#L64 string] db_defaults that will raise a system check error if `DatabaseFeatures.supports_expression_defaults = False`
since these models don't have `required_db_features = {""supports_expression_defaults""}`.

I'm working on MongoDB which doesn't support any database defaults, literal or expressions."	Bug	closed	Core (System checks)	5.0	Normal	fixed		Lily Foote	Ready for checkin	1	0	0	0	0	0
