The Basics
Django’s built-in support for MS SQL Server has some known issues, and there are a large number of patches for improving this support. Unfortunately, none of the core Django developers are Windows/SQL Server uses, so these patches tend not to get accepted.
mtredinnick suggested moving the SQL Server backend to a separate project, and here you are.
The goal of this project is to provide high-quality support for using MS SQL Server with Django, including introspection features and good data type mapping. Initial work will be based on the existing “ado-mssql” backend, getting it working without any patches to Django itself.
Future work may focus on migrating away from the current ADO wrapper to something under more current development.
Project Home – http://code.google.com/p/django-mssql/Grab the Repository – svn checkout http://django-mssql.googlecode.com/svn/trunk/
Recent Commits
-
94 was committed 2 days, 5 hours ago.
Removed table-name-spaces patch; this has been accepted into Django proper.
-
93 was committed 1 week ago.
Removed some now-unused DatabaseFeatures (due to http://code.djangoproject.com/changeset/7790 )
-
92 was committed 1 week ago.
Using “decimal” instead of “numeric” for the SQL Server column type (for DecimalField). In SQL Server these field types are identical behind the scenes, and it will help my sanity to use “decimal” instead. Either field type will still be introspected correctly.
-
91 was committed 1 week ago.
Tweaked a decimal test to fill the specified digits.
-
90 was committed 1 week ago.
Removed some code per issue 24.
-
89 was committed 1 week ago.
Added tests for issue 21.
-
88 was committed 1 week ago.
Removed datetime munging regex; don’t need it anymore.
-
87 was committed 1 week ago.
Added test cases and code fixes for issue 23.
-
86 was committed 1 week, 1 day ago.
Initial check-in for Dnango #5641.
-
84 was committed 3 weeks, 1 day ago.
Automating tests.