summaryrefslogtreecommitdiff
path: root/sqlparse/engine/statement_splitter.py
diff options
context:
space:
mode:
authorVictor Uriarte <victor.m.uriarte@intel.com>2017-11-29 09:56:06 -0700
committerVictor Uriarte <victor.m.uriarte@intel.com>2017-11-29 14:52:15 -0700
commit43478c60394e09246ee6275f89ae434e429cc5b5 (patch)
tree07c7cf589827d53212e38f54cc84bc88d56a1b5d /sqlparse/engine/statement_splitter.py
parent745df4576efca44b226bcdca33f718a5fa670eab (diff)
downloadsqlparse-typo.tar.gz
Fix typostypo
Diffstat (limited to 'sqlparse/engine/statement_splitter.py')
-rw-r--r--sqlparse/engine/statement_splitter.py6
1 files changed, 3 insertions, 3 deletions
diff --git a/sqlparse/engine/statement_splitter.py b/sqlparse/engine/statement_splitter.py
index 6c5b599..87fe993 100644
--- a/sqlparse/engine/statement_splitter.py
+++ b/sqlparse/engine/statement_splitter.py
@@ -29,7 +29,7 @@ class StatementSplitter(object):
# ANSI
# if normal token return
# wouldn't parenthesis increase/decrease a level?
- # no, inside a paranthesis can't start new statement
+ # no, inside a parenthesis can't start new statement
if ttype not in T.Keyword:
return 0
@@ -56,9 +56,9 @@ class StatementSplitter(object):
return 1
return 0
- # Should this respect a preceeding BEGIN?
+ # Should this respect a preceding BEGIN?
# In CASE ... WHEN ... END this results in a split level -1.
- # Would having multiple CASE WHEN END and a Assigment Operator
+ # Would having multiple CASE WHEN END and a Assignment Operator
# cause the statement to cut off prematurely?
if unified == 'END':
self._begin_depth = max(0, self._begin_depth - 1)