#29709 closed Cleanup/optimization (fixed)
Recommend the django-pyodbc-azure instead of Django-mssql as Microsoft SQL Server backend
| Reported by: | Rafael Reuber | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 2.1 |
| Severity: | Normal | Keywords: | sqlserver django-mssql |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The djando-msssql is not actively maintained. The last released version of Django-mssql supported Django 1.8. Few days ago the maintener of django-mssql announced the end-of-life and recommend switching to django-pyodbc-azure.
Please change the "Microsoft SQL Server" link on the session "Using a 3rd-party database backend" to point to https://pypi.org/project/django-pyodbc-azure/
Change History (3)
comment:1 by , 6 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|---|
| Type: | Uncategorized → Cleanup/optimization |
comment:2 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
In 7b7fb2ec: