From: Mike Bayer Date: Tue, 19 Mar 2024 14:51:01 +0000 (-0400) Subject: work around boldface concerns X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=697dcc94e412e013aba298e17613ee097f423e04;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git work around boldface concerns Change-Id: I99ed117bb0f1bdc1a8750bd13db5a69d5c398ae0 --- diff --git a/lib/sqlalchemy/dialects/postgresql/base.py b/lib/sqlalchemy/dialects/postgresql/base.py index 5b287564fb..e4e545e7d7 100644 --- a/lib/sqlalchemy/dialects/postgresql/base.py +++ b/lib/sqlalchemy/dialects/postgresql/base.py @@ -407,8 +407,8 @@ default schema, if one exists. Otherwise, ``public`` is used. When a :class:`_schema.Table` object is reflected, if it is present in the schema indicated by the ``current_schema()`` function, **the schema name assigned -to the table is the Python value ``None``**. Otherwise, the schema name -will be assigned as the name of that schema. +to the ".schema" attribute of the Table is the Python "None" value**. Otherwise, the +".schema" attribute will be assigned the string name of that schema. With regards to tables which these :class:`_schema.Table` objects refer to via foreign key constraint, a decision must be made as to how