Bug report #9007
MS SQL uniqueidentifier data type is not supported
| Status: | Closed | ||
|---|---|---|---|
| Priority: | High | ||
| Assignee: |  Nathan Woodrow | ||
| Category: | Data Provider/MSSQL | ||
| Affected QGIS version: | 2.0.1 | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | duplicate |
| Crashes QGIS or corrupts data: | Yes | Copied to github as #: | 17662 |
Description
If a MS SQL Spatial layer uses <uniqueidentifier> 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 <uniqueidentifier> 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 issues
History
#1
Updated by Nathan Woodrow over 10 years ago
- Assignee set to Nathan Woodrow
It seems QGIS only support int primary keys. I will do some more follow up.
#2
Updated by Nathan Woodrow over 10 years ago
- Status changed from Open to Feedback
#3
Updated by Ali Diba almost 10 years ago
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.
#4
Updated by Giovanni Manghi almost 10 years ago
- Status changed from Feedback to Open
#5
Updated by Nathan Woodrow over 9 years ago
- Resolution set to duplicate
- Status changed from Open to Closed
Closing in favor of #10946 as it will do the same thing once added.