My 2c;
The technical board has always done a stellar job of ensuring that good
ideas end up in the code base, and unfinished, unsupported, incomplete,
young, or non-reviewed code stays outside.
The quality of the core framework, and the ease of having 3rd party code
exist as Extensions, Plug-ins
Thanks for the feedback Adam. Your suggestions are actionable and potential
sponsorship has been raised for discussion as recently as this week (no
promises or strings attached).
We'll reach out to you directly if we have any direct follow-up on filling
in the feature gaps.
-Warren
On
Hi again Warren,
Good work on maintaining the backend.
Merging the backend could be a good end goal, but I'd be concerned about
merging it in the current state. The README lists many features that don't
work: https://github.com/microsoft/mssql-django#limitations . This list
includes some key
Hi All,
There is increasing interest within Microsoft to have stronger ties between
Microsoft SQL Server and Django. As you may be aware, Microsoft and their
connectivity teams have been managing the 3rd party backend for
"mssql-django" for over a year now at:
I currently have this sort of field in my model:
motivation = models.TextField(max_length=10_000, validators=[
MinLengthValidator(
100)])
And I am using CreateView with this model. The form generated by this view
has maxlength html attribute derived from the model's max_length, and it
makes for
Week ending March 27, 2022
*Triaged: *
https://code.djangoproject.com/ticket/33586 - Cannot delete object (A)
referenced by another object (B) if said object (A) has a foreign key to a
custom user. (accepted)
https://code.djangoproject.com/ticket/33589 - Incomplete string escaping
in
