Keep CRS for db layers with type GEOMETRY + more flexible type selection #451

Closed
wants to merge 1 commit into
from

Projects

None yet

2 participants

Contributor
mhugent commented Mar 1, 2013

Currently, if a db layer is of type GEOMETRY (or not contained in geometry_columns) and the search thread does not find an entry, it is always needed to enter the srid number. However, the table usually has already an srid. This patch keeps the srid if it is present.

Additionally, if the search thread has detected geometry objects, those types are added to the dialog. But if the user wants to open the layer with a new type (e.g. needs polygons even if currently there is no polygon in the table), it is not possible now. The patch always adds an extra line to select the type.

Please review.

@mhugent mhugent Consider crs for postgres layers with type GEOMETRY. Always provide t…
…he possibility to open a layer that has been detected by search thread as a different geometry type
36d2811
@jef-n jef-n was assigned Mar 1, 2013
@mhugent mhugent was assigned Sep 6, 2013
Contributor
mhugent commented Sep 6, 2013

test: assigned to @mhugent

Contributor
mhugent commented Sep 12, 2013

I think functionality similar to this pull request is already in master branch now, so closing

@mhugent mhugent closed this Sep 12, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment