summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/mssql/base.py
diff options
context:
space:
mode:
authorDiana Clarke <diana.joan.clarke@gmail.com>2012-03-17 21:41:58 -0400
committerDiana Clarke <diana.joan.clarke@gmail.com>2012-03-17 21:41:58 -0400
commit87fc12cc12894440683a80509acca975d3924eea (patch)
tree926917561b476b549d52d57c38d31dcd948aa129 /lib/sqlalchemy/dialects/mssql/base.py
parent4a7ee798509e51e21d441243202e30d8067f6144 (diff)
downloadsqlalchemy-87fc12cc12894440683a80509acca975d3924eea.tar.gz
typoes in lib/sqlalchemy/dialects
Diffstat (limited to 'lib/sqlalchemy/dialects/mssql/base.py')
-rw-r--r--lib/sqlalchemy/dialects/mssql/base.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/sqlalchemy/dialects/mssql/base.py b/lib/sqlalchemy/dialects/mssql/base.py
index 103b0a3e9..e58721586 100644
--- a/lib/sqlalchemy/dialects/mssql/base.py
+++ b/lib/sqlalchemy/dialects/mssql/base.py
@@ -107,10 +107,10 @@ Compatibility Levels
--------------------
MSSQL supports the notion of setting compatibility levels at the
database level. This allows, for instance, to run a database that
-is compatibile with SQL2000 while running on a SQL2005 database
+is compatible with SQL2000 while running on a SQL2005 database
server. ``server_version_info`` will always return the database
server version information (in this case SQL2005) and not the
-compatibiility level information. Because of this, if running under
+compatibility level information. Because of this, if running under
a backwards compatibility mode SQAlchemy may attempt to use T-SQL
statements that are unable to be parsed by the database server.