]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Support "blank" schema when MetaData.schema is set
authorMike Bayer <mike_mp@zzzcomputing.com>
Wed, 18 May 2016 15:07:02 +0000 (11:07 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Wed, 18 May 2016 15:44:56 +0000 (11:44 -0400)
commit4b31736343f113d7f7590a1b655ce0d334ea2fd5
tree57f24a26869581ab1975dfbdc0f185c35a090ee3
parentf500bfee855e147323b753790b557e2fe06b83e2
Support "blank" schema when MetaData.schema is set

Previously, it was impossible to have a Table that has
None for a schema name when the "schema" parameter on
MetaData was set.  A new symbol sqlalchemy.schema.BLANK_SCHEMA
is added which indicates that the schema name should unconditionally
be set to None.  In particular, this value must be passed within
cross-schema foreign key reflection, so that a Table which
is in the "default" schema can be represented properly.

Fixes: #3716
Change-Id: I3d24f99c22cded206c5379fd32a225e74edb7a8e
(cherry picked from commit c124fa36d5af2c85c87c51d24e92387adffbe3d2)
doc/build/changelog/changelog_10.rst
doc/build/core/metadata.rst
lib/sqlalchemy/__init__.py
lib/sqlalchemy/engine/reflection.py
lib/sqlalchemy/schema.py
lib/sqlalchemy/sql/schema.py
test/dialect/postgresql/test_reflection.py
test/engine/test_reflection.py
test/sql/test_metadata.py