From de5a4c544d96b28e3b05c61e17dc844a1b5caa2d Mon Sep 17 00:00:00 2001 From: Michael Trier Date: Sat, 3 Jan 2009 17:42:31 +0000 Subject: [PATCH] Added a note about mssql compatibility levels. --- lib/sqlalchemy/databases/mssql.py | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/lib/sqlalchemy/databases/mssql.py b/lib/sqlalchemy/databases/mssql.py index 9467c10882..0904d7b90a 100644 --- a/lib/sqlalchemy/databases/mssql.py +++ b/lib/sqlalchemy/databases/mssql.py @@ -200,6 +200,17 @@ render:: If ``nullable`` is ``True`` or ``False`` then the column will be ``NULL` or ``NOT NULL`` respectively. +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 +server. ``server_version_info`` will always retrun the database +server version information (in this case SQL2005) and not the +compatibiility 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. + Known Issues ------------ -- 2.47.3