Context Navigation

Changes between Version 1 and Version 2 of Ticket #35223

-              v1
+              v2
 Starting to migrate models in my (large) project to use Django 5’s new db_default attribute for fields (using Django 5.0.2), encountering behavior contrary to my expectations.
+Starting to migrate models in my (large) project to use Django 5’s new {{{db_default}}} attribute for fields (using Django 5.0.2), encountering behavior contrary to my expectations.
 A field with {{{db_default}}} raises a {{{ValidationError}}} when {{{full_clean()}}} called, if that field has been omitted from the {{{create()}}} call.
 …
 This is (to me) unexpected behavior. Would expect that no error would be raised, the instance would be saved successfully, with the specified {{{db_default}}} value set at the database level.
 Has been explained to me in the Django forums that this is correct, that I should instead either
+Has been explained to me in the Django forums that the {{{ValidationError}}} is correct, that I should instead either
 (1) explicitly choose to {{{exclude}}} the missing fields from {{{full_clean()}}} call,