Seems to me that if database backends were separate from Django then the postgres backend would get a long way ahead of the others as much as the other backends would get behind - it's bound to attract the most work and be adding custom fields like hstore, arrays, json... I think this would be great for most of my use cases, but then again I also have to deploy a small proportion of sites on MySQL, so it's bound to bite me.
That said, I don't know why Oracle is included and MSSQL is not - pretty much none of the core devs currently use either (or would recommend it given the choice). Cross compatibility of Django core is really important, and should ideally be as far reaching as we can achieve. I'd rather see MSSQL pulled in, and hopefully testing of it via Travis at some point than things split out, as I think it's better for Django. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
