summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/events.py
diff options
context:
space:
mode:
Diffstat (limited to 'lib/sqlalchemy/events.py')
-rw-r--r--lib/sqlalchemy/events.py12
1 files changed, 6 insertions, 6 deletions
diff --git a/lib/sqlalchemy/events.py b/lib/sqlalchemy/events.py
index 9ba6de68b..908ce378f 100644
--- a/lib/sqlalchemy/events.py
+++ b/lib/sqlalchemy/events.py
@@ -74,7 +74,7 @@ class DDLEvents(event.Events):
_dispatch_target = SchemaEventTarget
def before_create(self, target, connection, **kw):
- """Called before CREATE statments are emitted.
+ """Called before CREATE statements are emitted.
:param target: the :class:`.MetaData` or :class:`.Table`
object which is the target of the event.
@@ -90,7 +90,7 @@ class DDLEvents(event.Events):
"""
def after_create(self, target, connection, **kw):
- """Called after CREATE statments are emitted.
+ """Called after CREATE statements are emitted.
:param target: the :class:`.MetaData` or :class:`.Table`
object which is the target of the event.
@@ -106,7 +106,7 @@ class DDLEvents(event.Events):
"""
def before_drop(self, target, connection, **kw):
- """Called before DROP statments are emitted.
+ """Called before DROP statements are emitted.
:param target: the :class:`.MetaData` or :class:`.Table`
object which is the target of the event.
@@ -122,7 +122,7 @@ class DDLEvents(event.Events):
"""
def after_drop(self, target, connection, **kw):
- """Called after DROP statments are emitted.
+ """Called after DROP statements are emitted.
:param target: the :class:`.MetaData` or :class:`.Table`
object which is the target of the event.
@@ -348,7 +348,7 @@ class PoolEvents(event.Events):
The :meth:`.PoolEvents.reset` event is usually followed by the
- the :meth:`.PoolEvents.checkin` event is called, except in those
+ :meth:`.PoolEvents.checkin` event is called, except in those
cases where the connection is discarded immediately after reset.
:param dbapi_connection: a DBAPI connection.
@@ -611,7 +611,7 @@ class ConnectionEvents(event.Events):
This event is called with the DBAPI exception instance
received from the DBAPI itself, *before* SQLAlchemy wraps the
- exception with it's own exception wrappers, and before any
+ exception with its own exception wrappers, and before any
other operations are performed on the DBAPI cursor; the
existing transaction remains in effect as well as any state
on the cursor.