Opened 13 years ago
Closed 11 years ago
#7400 closed enhancement (duplicate)
transaction oriented upload to prevent trouble on aborts
| Reported by: | Zecke | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: | bastiK, stoecker, skyper |
Description
JOSM sollte den upload von Daten transaktionssicher implementieren. Es kann derzeit vorkommen, daß ein Benutzer den upload abbricht, weil er zu lange dauert und später wieder probiert. dabei kann es zu doppelt erzeugten Objekten kommen, was besonders schlimm ist, weil man es nicht merkt.
Ein unvollständiger upload sollte stets einen Rollback zur Folge haben.
Schön wäre es auch, wenn JOSM beim upload erkennen könnte, daß die entsprechenden Objekte Duplikate sind und eine entsprechende Warnung ausgeben.
Attachments (0)
Change History (5)
comment:1 by , 11 years ago
| Cc: | added |
|---|
comment:2 by , 11 years ago
wow, this ticket is antique!
JOSM should implement data transfer in a transaction safe manner. It occured that uploads, taking too long, get aborted by the user and tried again. This led to doubled objects in OSM. The user has no chance to realize this. It would be nice if JOSM could recognize doubled objects upon upload.
(don't know if it's still a problem today)
Zecke
comment:3 by , 11 years ago
I believe it is still an issue. Thought not ours, but of the API I think. They have no transaction handling like a DB. Until this is implemented JOSM can't fix this issue.
comment:4 by , 11 years ago
| Summary: | transaktionsorientierter upload → transaction oriented upload to prevent trouble on aborts |
|---|
comment:5 by , 11 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Closed as duplicate of #5214.
Can someone translate this ticket?