Opened 13 years ago

Last modified 12 years ago

#2001 new bug

Postgis Manager notes for enhancements/bug fixes

Reported by: lutra Owned by: wonder
Priority: major: does not work as expected Milestone: Version 1.7.0
Component: Python plugins and bindings Version: Trunk
Keywords: Cc:
Must Fix for Release: No Platform: All
Platform Version: Awaiting user input: no

Description

*) enhancement: when loading data from shapefiles, the "choose input shapefile" shows always the home folder (at least under linux) when it opens. It would be better to make it open in the last folder used, otherwise loading many shapefiles not located near the ~ become is very frustrating.

*) feature: allow multiple load from more than one shapefile at one time

*) bug: when a shapefile is loaded into postgis the table list is not refreshed in the database view

*) enhancement: when changing the table structure (by adding/deleting/editing columns) of a postgis layer that is loaded in the map canvas, refreshing the layer after the changes are applied. This already happens in qgis when you alter the table structure using the "properties -> attributes" menu.

*) bug: when adding/editing a column I get always an error if I try to define the length of the field.

*) enhancement: when adding/editing a column, when choosing a particular type, an error is returned if the "can be null" checkbox is not selected. For these particular types should be better to have the checkbox automatically selected.


this would fix among the others this two bugs I have found


*) In a postgis layer if I add a column with the "postgis manager", the attribute table is not immediately updated, as I have to reload the layer to see the changes. This doesn't happens if the column is added trough "Properties -> Attributes".

*) If I delete a postgis column with the "postgis manager" and the I open the attributes table I only see "ERROR" as values. If I reload the layer everything seems fine.

Change History (7)

comment:1 by lutra, 13 years ago

a few things have been fixed. This is what still remains (they still are just suggestions). I made things a little more clear/detailed if compared with the ticket description.

*) feature: allow multiple load from more than one shapefile at one time

*) In a postgis layer if I add/edit a column with the "postgis manager", the attribute table is not immediately updated, as I have to reload the layer to see the changes. This doesn't happens if the column is added trough "Properties -> Attributes".

*) If I delete a postgis column with the "postgis manager" and the I open the attributes table I only see "ERROR" as values. If I reload the layer everything seems fine.

*) bug: when adding/editing a column I get always an error if I try to define the length of the field. It seems that doesn't happens just with the "char" data type.

I see that "can be null" checkbox is selected by default, nevertheless I suggest that with datatypes that "cannot be null" to make the checkbox not active to avoid people uncheck it.

comment:2 by lutra, 12 years ago

Milestone: Version 1.5.0Version 1.6.0

comment:3 by pcav, 12 years ago

This is not a core plugin. The report should be moved to the new additional plugin tracker when ready.

in reply to:  3 comment:4 by lutra, 12 years ago

Replying to pcav:

This is not a core plugin. The report should be moved to the new additional plugin tracker when ready.

when reasy I'll do it ;) but I hope also that this plugin will become core

comment:5 by pcav, 12 years ago

It cannot for now, as it would introduce an heavy dependency (shp2pgsql and pgsql2shp, which means the whole PostgreSQL+PostGIS in Windows).

in reply to:  5 ; comment:6 by jef, 12 years ago

Replying to pcav:

It cannot for now, as it would introduce an heavy dependency (shp2pgsql and pgsql2shp, which means the whole PostgreSQL+PostGIS in Windows).

Why not? We don't include GDAL binaries either...

in reply to:  6 comment:7 by jef, 12 years ago

Replying to jef:

Replying to pcav: Why not? We don't include GDAL binaries either...

In our repository that is. And shp2pgsql/pgsql2shp doesn't require more than a PostgreSQL connection - just like QGIS itself.

Note: See TracTickets for help on using tickets.