diff options
| author | Hannes Hansen <hannes.jakob.hansen@cern.ch> | 2019-05-23 16:27:21 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2019-05-27 16:57:37 -0400 |
| commit | c55023641d390b2b09601b10dbc5663e4bd5a466 (patch) | |
| tree | 72b58c77440b9247691e298c39f3c97d9b3de480 /lib/sqlalchemy/sql/expression.py | |
| parent | 90882ed43cce26c069b6696b441b6ad8a7372301 (diff) | |
| download | sqlalchemy-c55023641d390b2b09601b10dbc5663e4bd5a466.tar.gz | |
MYSQL: added support for drop check/constraint
Added support for DROP CHECK constraint which is required by MySQL 8.0.16
to drop a CHECK constraint; MariaDB supports plain DROP CONSTRAINT. The
logic distinguishes between the two syntaxes by checking the server version
string for MariaDB presence. Alembic migrations has already worked
around this issue by implementing its own DROP for MySQL / MariaDB CHECK
constraints, however this change implements it straight in Core so that its
available for general use. Pull request courtesy Hannes Hansen.
Fixes: #4650
Closes: #4659
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4659
Pull-request-sha: 5b654a55e23c2ca498ca3b1cae4f53859e93e8f7
Change-Id: I967710f890722f11cf1f40406adbb17464d16194
Diffstat (limited to 'lib/sqlalchemy/sql/expression.py')
0 files changed, 0 insertions, 0 deletions