-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add native support for UUID data type #134
Comments
The reason this is not supported by default is because mssql-django uses char(32) not uniqueidentifier as the UUIDField which can be seen in Line 118 in 5823873
By just changing the has_native_uuid_field to True it causes some unit test to fail, which is why PR #135 is failing the pipeline. |
Any interest here? My use-case, is that django is not the only application touching the database and it's not handling the migrations at all (however they're used in testing and development). My workaround is to use a charfield, which is less than satisfying. Tagging #40, since it's related to this. |
I have a similar situation to @XF-FW and would really like to see native support for UUID. |
It would be really nice to have it implemented. Are there any plans, guys? |
Hi @DrMeosch , we will be reinvestigating the scope of work here and update you on our findings. Thank you |
We're planning to have native support for UUID's in the next release. Thanks everyone for chiming in |
These changes were reverted because of #363. Could you reopen the issue? |
I keep getting this error [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Conversion failed when converting from a character string to uniqueidentifier.
And the problem is because mssql-django does not use uniqueidentifier as the data type for UUIDFields,
I change the has_native_uuid_field to True and it's working. Also created a PR #135
Is there any reason to why this is not support by default?
The text was updated successfully, but these errors were encountered: