microsoft / mssql-django

The Microsoft Django backend for SQL Server provides a connectivity layer for Django on SQL Server or Azure SQL DB.
Other
350 stars 115 forks source link

Compatibility issue with Django 5.1 #418

Open bdr-sara opened 3 weeks ago

bdr-sara commented 3 weeks ago

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

Software versions

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 commented 3 days ago

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