Compatibility issue with Django 5.1

[bdr-sara]

There are some features which are not supported yet. Please check the Limitations first to see if your bug is listed.

Software versions

• Django:5.1.2
• mssql-django:1.5
• python:313
• SQL Server:17
• OS:windows11

Table schema and Model

class ComponentLinkType(models.Model):
id = models.AutoField(db_column='ID', primary_key=True) # Field name made lowercase.
name_type_link = models.CharField(db_column='Name_Type_Link', max_length=255, blank=True, null=True) # Field name made lowercase.
name_type_en_short = models.CharField(db_column='Name_Type_EN_Short', max_length=50, blank=True, null=True) # Field name made lowercase.
name_type_heb = models.CharField(db_column='Name_Type_HEB', max_length=50, blank=True, null=True) # Field name made lowercase.

class Meta:
    managed = False
    db_table = 'Component_Link_Type'

Database Connection Settings
'ENGINE': 'mssql',

Problem description and steps to reproduce
Updated pip install pyodbc==5.2.0
Updated Django to version 5.1.2.
Installed mssql-django version 1.5 as the database backend.
Ran pip install --upgrade django to update Django.
Encountered a dependency conflict error during the installation due to mssql-django requiring Django < 5.1.
Expected behavior and actual behavior
mssql-django should support Django 5.1 to be compatible with the latest features and security updates. Actual: The current version of mssql-django only supports up to Django 5.0.x, causing a dependency conflict with Django 5.1.x.

Error message/stack trace
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
mssql-django 1.5 requires django<5.1,>=3.2, but you have django 5.1.2 which is incompatible.

Any other details that can be helpful
It would be helpful to know if there are plans to support Django 5.1.x soon or if a workaround exists for users needing compatibility with this version.

[maclinbc]

This Pull Request solved alot of my issues
https://github.com/microsoft/mssql-django/pull/397/commits

[rjschave]

@David-Engel,

It seems you were involved in getting Microsoft to support the the mssql driver for Django back in 2021 (michiya/django-pyodbc-azure#190 and FlipperPA/django#8). The result is this project.

This project has supported Django through version 5.0. There was some effort to update this project to support Django 5.1, but it appears that effort stalled in May. There has been no activity in this repo for 3+ months.

This is a "Microsoft project", but it's not clear to me the maintainers work at/for Microsoft. I'm concerned they have moved on from Microsoft or have been reassigned. Do you have any contact with the folks that had been maintaining this project.

The lack of activity is making some of us nervous. I guess I'm looking for some indication on whether efforts will resume or if this project has been abandoned abandoned.

Thank you.

[maclinbc]

@David-Engel,

It seems you were involved in getting Microsoft to support the the mssql driver for Django back in 2021 (michiya/django-pyodbc-azure#190 and FlipperPA/django#8). The result is this project.

This project has supported Django through version 5.0. There was some effort to update this project to support Django 5.1, but it appears that effort stalled in May. There has been no activity in this repo for 3+ months.

This is a "Microsoft project", but it's not clear to me the maintainers work at/for Microsoft. I'm concerned they have moved on from Microsoft or have been reassigned. Do you have any contact with the folks that had been maintaining this project.

The lack of activity is making some of us nervous. I guess I'm looking for some indication on whether efforts will resume or if this project has been abandoned abandoned.

Thank you.

Someone may have to Fork it and take over if MS for (whatever reason?) abandoned the support.

[rjschave]

Someone may have to Fork it and take over if MS for (whatever reason?) abandoned the support.

I thought I might be able to work at the 5.1 branch, but It appears we can't even see why the tests are failing. The test suite runs on Azure Pipelines and the results don't appear to be public. Before I work to get the tests set up on my own infra, I wanted to find out if this project has been abandoned.

The reality is I may not have the skillset or time to take this over.

[David-Engel]

This project hasn't been abandoned. But we did lose some individual contributors. We have some resources that will be taking over this project, but they are currently focused on a different effort in the Python space. We do plan to loop back around to this one.

[ygorcf]

Hello, im waiting for this feature by a month, and seeing the last comment, i cant only sit and wait, so i will try to continue the PR.

[spapas]

It's like 6 months and we still don't have Django 5.1 compatibility. Any idea when the django51 branch will be merged? It seems to be working fine for me!

For people that need it:

pip install git+https://github.com/microsoft/mssql-django@django51