Hi Michael,
On 27 May 2016, at 20:44, Michael Manfre wrote:
> Regarding feature parity, the initial commit of this non-existent-yet library
> will have as many supported features as django-mssql on Django 1.9 and 1.10.
> :P
Fair enough :-)
> The pre-release code will need to be hosted public
Aymeric wrote:
> However I’m wary of deciding that a non-existent-yet library is the
> endorsed solution for using SQL Server from Django. It may be best to wait
> until it has reached feature parity with django-mssql and received some
> amount of real-world testing to move it there.
>
Regarding
Hi Michael,
> To me the most important reason is, I want to start from scratch to help
document what is involved with creating a database backend.
I agree, such documentation is definitely lacking and even if it wont be
commonly used it's invaluable for the rare developers needing it.
Are you
I'm definitely a fan of doing things under the /django banner. I think so
long as we make it clear that this is in development then it shouldn't
matter about feature parity - especially as django-mssql won't have a
version supporting 1.9 or 1.10 anyway.
On 27 May 2016 at 08:24, Aymeric Augustin <
Hi Michael,
Thanks for this initiative!
I like the idea of hosting this new project in the Django organization. I think
there’s a lot of value in having a good SQL Server backend for Django,
implemented according to Microsoft’s recommendations, and little reason to
encourage competition in thi
There are two parts to this email. First relates to the current state of
django-mssql. A version of the backend that supports Django 1.8 will be
released in the next few weeks. I apologize for the delay, but my ability
to focus on the project was basically non-existent for nearly a year due to
pers
