summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/postgresql/base.py
diff options
context:
space:
mode:
authorGord Thompson <gord@gordthompson.com>2021-03-06 12:19:13 -0700
committerMike Bayer <mike_mp@zzzcomputing.com>2021-03-06 22:27:59 -0500
commit506b88de5e428fd4ad2feff663ba53e2dbb28891 (patch)
tree4da8bb1166928480cec3dc9668d1a1a6175dd087 /lib/sqlalchemy/dialects/postgresql/base.py
parent1f3ef9817453faa021544841d10b5b7107b57916 (diff)
downloadsqlalchemy-506b88de5e428fd4ad2feff663ba53e2dbb28891.tar.gz
Fix named CHECK constraint name omitted on repeated creates
Fixed issue where the CHECK constraint generated by :class:`_types.Boolean` or :class:`_types.Enum` would fail to render the naming convention correctly after the first compilation, due to an unintended change of state within the name given to the constraint. This issue was first introduced in 0.9 in the fix for issue #3067, and the fix revises the approach taken at that time which appears to have been more involved than what was needed. Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Fixes: #6007 Change-Id: I7ecff0a9d86191520f6841b3922a5af5a6971fba
Diffstat (limited to 'lib/sqlalchemy/dialects/postgresql/base.py')
0 files changed, 0 insertions, 0 deletions