diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2017-03-18 14:57:41 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2017-03-18 14:57:41 -0400 |
| commit | 9e06ab17b9d3083cd45540f714234d1d5826da32 (patch) | |
| tree | 33cc1967577921be95b0b18b09130b224076eb75 /doc | |
| parent | a40467152cbbc7e65d629dafbcc04ad1c85d3025 (diff) | |
| parent | 3771af0af45c2a7ea79a055b953c32f23c53e256 (diff) | |
| download | sqlalchemy-9e06ab17b9d3083cd45540f714234d1d5826da32.tar.gz | |
Merge branch 'master' of https://bitbucket.org/jalessio/sqlalchemy
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/build/core/constraints.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/core/constraints.rst b/doc/build/core/constraints.rst index aff684f0a..88d003678 100644 --- a/doc/build/core/constraints.rst +++ b/doc/build/core/constraints.rst @@ -415,7 +415,7 @@ produced inline with the table definition, the database usually has a system in place in which names are automatically assigned to these constraints, if a name is not otherwise specified. When an existing database table is altered in a database using a command such as ``ALTER TABLE``, this command typically -needs to specify expicit names for new constraints as well as be able to +needs to specify explicit names for new constraints as well as be able to specify the name of an existing constraint that is to be dropped or modified. Constraints can be named explicitly using the :paramref:`.Constraint.name` parameter, |