summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJamie Alessio <jamie@calthorpeanalytics.com>2017-03-14 19:02:38 -0700
committerJamie Alessio <jamie@calthorpeanalytics.com>2017-03-14 19:04:03 -0700
commit3771af0af45c2a7ea79a055b953c32f23c53e256 (patch)
tree40c23b409535d47e86df35bb275d737a475fdefa
parent0a35ccc6bd1acaa91f32c8e0140000b19ae85e14 (diff)
downloadsqlalchemy-3771af0af45c2a7ea79a055b953c32f23c53e256.tar.gz
Fix typos ('expicit' -> 'explicit')
-rw-r--r--doc/build/core/constraints.rst2
-rw-r--r--lib/sqlalchemy/sql/schema.py4
-rw-r--r--test/sql/test_insert_exec.py2
3 files changed, 4 insertions, 4 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,
diff --git a/lib/sqlalchemy/sql/schema.py b/lib/sqlalchemy/sql/schema.py
index e6eabc461..66996145f 100644
--- a/lib/sqlalchemy/sql/schema.py
+++ b/lib/sqlalchemy/sql/schema.py
@@ -175,7 +175,7 @@ class Table(DialectKWArgs, SchemaItem, TableClause):
is set in which case it defaults to True; :class:`.Column` objects
for this table should be reflected from the database, possibly
augmenting or replacing existing :class:`.Column` objects that were
- expicitly specified.
+ explicitly specified.
.. versionchanged:: 1.0.0 setting the :paramref:`.Table.autoload_with`
parameter implies that :paramref:`.Table.autoload` will default
@@ -3552,7 +3552,7 @@ class MetaData(SchemaItem):
present, the :class:`.Constraint` object's existing name will be
replaced with one that is composed from template string that
uses this token. When this token is present, it is required that
- the :class:`.Constraint` is given an expicit name ahead of time.
+ the :class:`.Constraint` is given an explicit name ahead of time.
* user-defined: any additional token may be implemented by passing
it along with a ``fn(constraint, table)`` callable to the
diff --git a/test/sql/test_insert_exec.py b/test/sql/test_insert_exec.py
index c49947425..6015f4e74 100644
--- a/test/sql/test_insert_exec.py
+++ b/test/sql/test_insert_exec.py
@@ -328,7 +328,7 @@ class TableInsertTest(fixtures.TablesTest):
data)
@testing.requires.sequences
- def test_expicit_sequence(self):
+ def test_explicit_sequence(self):
t = self._fixture()
self._test(
t.insert().values(