From 1a9d80ab4769951b1153276a026bd610010941df Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 9 Jan 2026 09:19:22 -0500 Subject: [PATCH] remove paragraph re: init=False as I think this is a 2.1 thing Change-Id: I78a61f75a2288e6823704cd10fcbbdb52352a25d --- doc/build/faq/ormconfiguration.rst | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/doc/build/faq/ormconfiguration.rst b/doc/build/faq/ormconfiguration.rst index a2c8ef9326..ba449d76dc 100644 --- a/doc/build/faq/ormconfiguration.rst +++ b/doc/build/faq/ormconfiguration.rst @@ -414,17 +414,6 @@ explicitly passed. Using this parameter is **mutually exclusive** against the :paramref:`_schema.Column.insert_default` parameter, meaning that both cannot be used at the same time. -The :paramref:`_orm.mapped_column.default` and -:paramref:`_orm.mapped_column.insert_default` parameters may also be used -(one or the other, not both) -for a SQLAlchemy-mapped dataclass field, or for a dataclass overall, -that indicates ``init=False``. -In this usage, if :paramref:`_orm.mapped_column.default` is used, the default -value will be available on the constructed object immediately as well as -used within the INSERT statement. If :paramref:`_orm.mapped_column.insert_default` -is used, the constructed object will return ``None`` for the attribute value, -but the default value will still be used for the INSERT statement. - For the specific case of using a callable to generate defaults, the situation changes a bit; the :paramref:`_orm.mapped_column.default_factory` parameter is a **dataclass only** parameter that may be used to generate new default values -- 2.47.3