diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-09-09 16:54:25 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-09-09 16:54:25 -0400 |
| commit | 78b8f627579a34891de75636726c67ebcf881e34 (patch) | |
| tree | 95a6aad22c16dba45d915be18bc95a8bc7f0f7cf | |
| parent | a2cd65bca9c4e802bdb04d9b254efb07eea8bebc (diff) | |
| download | alembic-cleanup.tar.gz | |
- update naming convention link to point to official docscleanup
| -rw-r--r-- | alembic/operations.py | 12 |
1 files changed, 4 insertions, 8 deletions
diff --git a/alembic/operations.py b/alembic/operations.py index dfc177b..94cbc36 100644 --- a/alembic/operations.py +++ b/alembic/operations.py @@ -516,8 +516,7 @@ class Operations(object): :param name: Name of the primary key constraint. The name is necessary so that an ALTER statement can be emitted. For setups that use an automated naming scheme such as that described at - `NamingConventions <http://www.sqlalchemy.org/trac/wiki/UsageRecipes/\ - NamingConventions>`_, + :ref:`sqla:constraint_naming_conventions` ``name`` here can be ``None``, as the event listener will apply the name to the constraint object when it is associated with the table. @@ -559,8 +558,7 @@ class Operations(object): :param name: Name of the foreign key constraint. The name is necessary so that an ALTER statement can be emitted. For setups that use an automated naming scheme such as that described at - `NamingConventions <http://www.sqlalchemy.org/trac/wiki/UsageRecipes/\ - NamingConventions>`_, + :ref:`sqla:constraint_naming_conventions`, ``name`` here can be ``None``, as the event listener will apply the name to the constraint object when it is associated with the table. @@ -616,8 +614,7 @@ class Operations(object): :param name: Name of the unique constraint. The name is necessary so that an ALTER statement can be emitted. For setups that use an automated naming scheme such as that described at - `NamingConventions <http://www.sqlalchemy.org/trac/wiki/UsageRecipes/\ - NamingConventions>`_, + :ref:`sqla:constraint_naming_conventions`, ``name`` here can be ``None``, as the event listener will apply the name to the constraint object when it is associated with the table. @@ -664,8 +661,7 @@ class Operations(object): :param name: Name of the check constraint. The name is necessary so that an ALTER statement can be emitted. For setups that use an automated naming scheme such as that described at - `NamingConventions <http://www.sqlalchemy.org/trac/wiki/UsageRecipes/\ - NamingConventions>`_, + :ref:`sqla:constraint_naming_conventions`, ``name`` here can be ``None``, as the event listener will apply the name to the constraint object when it is associated with the table. |