-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add conflict management to offline editing #23146
Comments
Author Name: Giovanni Manghi (@gioman) I think that this is how the tool is intended to work. It could be improved, but that would be a feature request, not a bug. Meanwhile you may want to look to this plugin https://github.com/Oslandia/qgis-versioning
|
Author Name: Matthias Kuhn (@m-kuhn)
|
Author Name: Matthias Kuhn (@m-kuhn)
|
Author Name: Giovanni Manghi (@gioman)
|
The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". |
While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue. |
Author Name: colin east (colin east)
Original Redmine Issue: 15208
Redmine category:c++_plugins/offline_editing
I wanted to understand if the Offline tool could be used for concurrent editing. The idea is to have the organisation's primary data stored in a PostGIS database. If an Offline project was created, could a user safely make edits to the primary data (source). However, it appears that the Offline tool will overwrite edits made to source data.
Test workflow:
Create Offline project for a PostGIS point layer.
Toggle editing on and move a single point by dragging it to a new llocation.
Save edit and toggle editing off of the Offline project layer.
Add source PostGIS layer.
Edit the same point in the source layer by to a different location.
Save and toggle editing off.
Synchronise the Offline project.
Outcome: Source layer edit is overwritten by Offline project with no warning.
Note: If this how the tool is designed then locking the layer could be and option. There is some discussion about table/row locking in #11031
The way the tool currently works means that if an Offline project is created then the source data cannot be modified until the Offline project is synchronised. This would not be workable for many business applications. It would good if a check could be run against the source data (perhaps a comparison of a row's last modified time stamp) to identify features that were modified after the Offline project was created so that the user can determine which edits are appropriate.
Related issue(s): #11031 (relates)
Redmine related issue(s): 972
The text was updated successfully, but these errors were encountered: