Ticket #2107 (closed enhancement: wontfix)

Opened 4 years ago

Last modified 4 years ago

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:
Platform Version: Kubuntu Jaunty Platform: All
Must Fix for Release: No 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

  Changed 4 years ago by lutra

  • priority changed from critical: causes crash or data corruption to minor: annoyance
  • platform changed from Linux to All
  • milestone changed from Version 1.0.3 to Version 1.4.0

follow-up: ↓ 3   Changed 4 years ago by jef

  • status changed from new to closed
  • resolution set to wontfix

it's just starting with the first field. What would be the alternative?

in reply to: ↑ 2   Changed 4 years ago by brianedmond

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.