diff options
| author | Michael Trier <mtrier@gmail.com> | 2009-01-03 17:42:31 +0000 |
|---|---|---|
| committer | Michael Trier <mtrier@gmail.com> | 2009-01-03 17:42:31 +0000 |
| commit | de5a4c544d96b28e3b05c61e17dc844a1b5caa2d (patch) | |
| tree | eb02101630256f74578566627e222b9935e77996 /lib/sqlalchemy/databases/mssql.py | |
| parent | ba2bd53ec9709fe5ce26012ea06a85511b2bef33 (diff) | |
| download | sqlalchemy-de5a4c544d96b28e3b05c61e17dc844a1b5caa2d.tar.gz | |
Added a note about mssql compatibility levels.
Diffstat (limited to 'lib/sqlalchemy/databases/mssql.py')
| -rw-r--r-- | lib/sqlalchemy/databases/mssql.py | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/lib/sqlalchemy/databases/mssql.py b/lib/sqlalchemy/databases/mssql.py index 9467c1088..0904d7b90 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 ------------ |