Passes most of the Django Test Suite?

[FlipperPA]

Greetings,

First off, thanks for the amazing work on django-pyodbc. We've been looking at moving our organization to Django, but have many projects which require SQL Server (a common refrain in these parts).

We hope to use django-pyodbc but this statement is a bit concerning: "Passes most of the tests of the Django test suite." I'm going to run the whole suite tomorrow to find out specifics, but even so, I was hoping the contributors to this repo could elaborate on this statement a bit, and what should be concerning if we consider running this in production. What are the key parts of it that fail - and how can we contribute to make it pass all the tests?

Are the fails on elements that don't exist in SQL Server, or didn't, like pagination support with TOP / OFFSET values? Are these test failures done strictly through Django's ORM? In other words: if we were running Rails, Grails, Symfony, etc, would we merely be seeing the limitations of the underlying database, or are we seeing things that can be done? Comments from the experts / contributors would be most appreciated.

We're more than happy to contribute, as we have with Pydanny's Two Scoops default project, and a few others.

We're also working on releasing an improved Django vagrant repo, once we get the chrome polished, which includes built in options to connect to SQL Server or any of the core-supported Django DBs.

Thanks again in advance.

[FlipperPA]

To follow up, I haven't had a chance to run the test suite against our setup (as you saw in my other post, heh), but I did find this on the deprecated version page, along with the same test of "Passes most of the Django test suite". Is this still accurate?

Currently, the following parts of the Django test suite don't pass:

lookup: Regular expressions are not supported out of the box by SQL Server. Only simple wildcard matching with %, _ and [] character classes.
serializers: Forward references cause foreign key constraint violation.