Skip to main content
new url
Source Link
Paul Ramsey
  • 20k
  • 2
  • 49
  • 58

Since you're not worried about simultaneous edits on features, I'd say that in theory you have nothing to worry about. The main danger w/ QGIS is that simultaneous editors can stomp on each other's edits without noticing ("last edit wins").

For data under active editing with multiple users you might want to at least keep track of history, which you can do w/o changing anything about QGIS, just adding some triggers and a history table to your active tables.

http://workshops.boundlessgeo.com/postgis-intro/history_tracking.htmlhttp://postgis.net/workshops/postgis-intro/history_tracking.html

That way if you ever want to revert changes you'll have a place to go that's easier to access than the database backups and point-in-time recovery.

Since you're not worried about simultaneous edits on features, I'd say that in theory you have nothing to worry about. The main danger w/ QGIS is that simultaneous editors can stomp on each other's edits without noticing ("last edit wins").

For data under active editing with multiple users you might want to at least keep track of history, which you can do w/o changing anything about QGIS, just adding some triggers and a history table to your active tables.

http://workshops.boundlessgeo.com/postgis-intro/history_tracking.html

That way if you ever want to revert changes you'll have a place to go that's easier to access than the database backups and point-in-time recovery.

Since you're not worried about simultaneous edits on features, I'd say that in theory you have nothing to worry about. The main danger w/ QGIS is that simultaneous editors can stomp on each other's edits without noticing ("last edit wins").

For data under active editing with multiple users you might want to at least keep track of history, which you can do w/o changing anything about QGIS, just adding some triggers and a history table to your active tables.

http://postgis.net/workshops/postgis-intro/history_tracking.html

That way if you ever want to revert changes you'll have a place to go that's easier to access than the database backups and point-in-time recovery.

deleted 2 characters in body
Source Link
Paul Ramsey
  • 20k
  • 2
  • 49
  • 58

Since you're not worried about simultaneous edits on features, I'd say that in theory you have nothing to worry about. The main danger w/ QGIS is that simultaneous editors can stomp on each other's edits without noticing ("last edit wins").

For data under active editing with multiple users you might want to at least keep track of history, which you can do w/o changing anything about QGIS, just adding some triggers and a history table to your active tables.

http://suite.opengeo.org/4.1/dataadmin/pgAdvanced/history_tracking.htmlhttp://workshops.boundlessgeo.com/postgis-intro/history_tracking.html

That way if you ever want to revert changes you'll have a place to go that's easier to access than the database backups and point-in-time recovery.

Since you're not worried about simultaneous edits on features, I'd say that in theory you have nothing to worry about. The main danger w/ QGIS is that simultaneous editors can stomp on each other's edits without noticing ("last edit wins").

For data under active editing with multiple users you might want to at least keep track of history, which you can do w/o changing anything about QGIS, just adding some triggers and a history table to your active tables.

http://suite.opengeo.org/4.1/dataadmin/pgAdvanced/history_tracking.html

That way if you ever want to revert changes you'll have a place to go that's easier to access than the database backups and point-in-time recovery.

Since you're not worried about simultaneous edits on features, I'd say that in theory you have nothing to worry about. The main danger w/ QGIS is that simultaneous editors can stomp on each other's edits without noticing ("last edit wins").

For data under active editing with multiple users you might want to at least keep track of history, which you can do w/o changing anything about QGIS, just adding some triggers and a history table to your active tables.

http://workshops.boundlessgeo.com/postgis-intro/history_tracking.html

That way if you ever want to revert changes you'll have a place to go that's easier to access than the database backups and point-in-time recovery.

Source Link
Paul Ramsey
  • 20k
  • 2
  • 49
  • 58

Since you're not worried about simultaneous edits on features, I'd say that in theory you have nothing to worry about. The main danger w/ QGIS is that simultaneous editors can stomp on each other's edits without noticing ("last edit wins").

For data under active editing with multiple users you might want to at least keep track of history, which you can do w/o changing anything about QGIS, just adding some triggers and a history table to your active tables.

http://suite.opengeo.org/4.1/dataadmin/pgAdvanced/history_tracking.html

That way if you ever want to revert changes you'll have a place to go that's easier to access than the database backups and point-in-time recovery.