[QGIS-trac] Re: [Quantum GIS] #972: do locking when features are
changed in PostGIS tables
Quantum GIS
qgis at qgis.org
Mon Jul 14 18:58:20 EDT 2008
#972: do locking when features are changed in PostGIS tables
-----------------------------------------------------+----------------------
Reporter: msieczka | Owner: jef
Type: enhancement | Status: new
Priority: major: does not work as expected | Milestone: Version 2.0.0
Component: Data Provider | Version: HEAD
Resolution: | Keywords:
Platform_version: | Platform: All
Must_fix: No | Status_info: 0
-----------------------------------------------------+----------------------
Comment (by timlinux):
A note on the meaning of 'major: does not work as expected'. This
assignment should be used when a feature has been implemented (e.g.
digitise a line) but some issue prevents the feature working. Minor
priority should be used where by design or ommission a feature has not
been implemented yet. In the case of this ticket I would contend the
priority to be 'minor'. I'll leave the priority as is and let the chips
fall where they may in this case....
--
Ticket URL: <http://trac.osgeo.org/qgis/ticket/972#comment:12>
Quantum GIS <http://qgis.org>
Quantum GIS is an Open Source GIS viewer/editor supporting OGR, PostGIS, and GRASS formats
More information about the QGIS-trac
mailing list