Skip to content
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

MS SQL uniqueidentifier data type is not supported #17662

Closed
qgib opened this issue Nov 4, 2013 · 5 comments
Closed

MS SQL uniqueidentifier data type is not supported #17662

qgib opened this issue Nov 4, 2013 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Data Provider Related to specific vector, raster or mesh data providers High Priority

Comments

@qgib
Copy link
Contributor

qgib commented Nov 4, 2013

Author Name: Ali Diba (Ali Diba)
Original Redmine Issue: 9007
Affected QGIS version: 2.0.1
Redmine category:data_provider/mssql
Assignee: Nathan Woodrow


If a MS SQL Spatial layer uses data type then layer attribute table displays as all nulls and the feature selection selects all features at all time (even if you select a single feature). In my test the was the PK of the attribute table. Incidentally the this SQL Spatial layer originated from ESRI where the datatype GUID (global id) was use to create it.

I have attached a script to help you recreate this problem. It creates a SQL Spatial table and loads it with some data.



Related issue(s): #19299 (relates), #20502 (relates)
Redmine related issue(s): 10946, 12324


@qgib
Copy link
Contributor Author

qgib commented Jun 1, 2014

Author Name: Nathan Woodrow (@NathanW2)


It seems QGIS only support int primary keys. I will do some more follow up.


  • assigned_to_id was configured as Nathan Woodrow

@qgib
Copy link
Contributor Author

qgib commented Jun 1, 2014

Author Name: Nathan Woodrow (@NathanW2)


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Nov 23, 2014

Author Name: Ali Diba (Ali Diba)


Brighton desktop crashes when you display the attribute table for a SQL Server Spatial layers that has a GUID field. Minidump is attached for your consideration.

@qgib
Copy link
Contributor Author

qgib commented Nov 23, 2014

Author Name: Giovanni Manghi (@gioman)


  • status_id was changed from Feedback to Open

@qgib
Copy link
Contributor Author

qgib commented May 31, 2015

Author Name: Nathan Woodrow (@NathanW2)


Closing in favor of #19299 as it will do the same thing once added.


  • resolution was changed from to duplicate
  • status_id was changed from Open to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Data Provider Related to specific vector, raster or mesh data providers Crash/Data Corruption labels May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Data Provider Related to specific vector, raster or mesh data providers High Priority
Projects
None yet
Development

No branches or pull requests

1 participant