#2107 closed enhancement (wontfix)
Classify vector features shouldn't default to gid on postgis features
| Reported by: | BrianEdmond | Owned by: | nobody |
|---|---|---|---|
| Priority: | minor: annoyance | Milestone: | Version 1.4.0 |
| Component: | Symbology | Version: | 1.3.0 |
| Keywords: | Cc: | ||
| Must Fix for Release: | No | Platform: | All |
| Platform Version: | Kubuntu Jaunty | Awaiting user input: | no |
Description
To reproduce, add any postgis layer, open layer properties, click on symbology, select "Unique Value" as the legend type. The default classification field is the gid which isn't a reasonable choice. I accidentally clicked the classify button without thinking on a very large postgis layer and it almost brought my machine down.
Change History (3)
comment:1 by , 14 years ago
| Milestone: | Version 1.0.3 → Version 1.4.0 |
|---|---|
| Platform: | Linux → All |
| Priority: | critical: causes crash or data corruption → minor: annoyance |
follow-up: 3 comment:2 by , 14 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:3 by , 14 years ago
Replying to jef:
it's just starting with the first field. What would be the alternative?
Well, you could calculate the number of features that will be classified and warn that it will take a long time if there are more than x number of features. I'm not sure what the threshold would be, but it would stop the application (and maybe someone's computer) from freezing up.
Note:
See TracTickets
for help on using tickets.
it's just starting with the first field. What would be the alternative?