Changes between Version 158 and Version 159 of BackwardsIncompatibleChanges

Timestamp:

Mar 26, 2008, 3:30:39 AM (16 years ago)

Author:

Malcolm Tredinnick

Comment:

ado_msql removal

BackwardsIncompatibleChanges

@@ -53 +53 @@
  * [7133] Feb 18, 2008 [#ChangedField.get_internal_typedefault Changed Field.get_internal_type() default]
  * [7153] Feb 25, 2008 [#Changeddecoratorstoinheritattributesofthefunctiontheywrap Changed decorators to inherit attributes of the function they wrap]
+ * [7364] March 26, 2008 [#Removedado_mssql Removed ado_mssql]
 
 == Database constraint names changed ==
@@ -577 +578 @@
 
 If you were using one of Django's decorators and relying on decorated functions/methods to have the name (`__name__`), docstring (`__doc__`), or attributes (`__dict__`) of the decorator, then you need to change your code to work off the name, docstring, or attributes of the decorated function instead.  If you are using Python 2.3, you don't need to worry about the changing of the decorated function's name since Python 2.3 does not support assignment to `__name__`.
+
+== Removed ado_mssql ==
+
+The unmaintained `ado_mssql` backend was removed in [7364]. Since external database backends can be used with Django, people wishing to contribute to or utilise Django support on Microsoft's SQL Server should have a look at external projects such as:
+
+ * http://code.google.com/p/django-mssql/
+ * http://code.google.com/p/django-pyodbc/
+
+Django's maintainers do not make any recommendations as to which of these (or alternate projects) may be better at this time, since none of us regularly develop on Windows or with SQL Server.