Bug #3459

Improve control over combining write transactions into undoable operations /Tu

Added by Tuukka Lehtonen over 5 years ago. Updated over 5 years ago.

Status:ClosedStart date:
Priority:4Due date:
Assignee:Tuukka Lehtonen% Done:

100%

Category:DB clientSpent time:-
Target version:2012-9
Release notes:
Story points3.0
Velocity based estimate-
ReleaseSimantics 1.6Release relationshipAuto

Description

Currently the only way to combine separate graph history revisions (transactions) into a single undoable operation is to invoke WriteGraph.asyncExec(Write) or any other write request - while in a database change/query listener. This is very limiting.

As a first improvement step, we want that:
  • Invocation of any WriteGraph.asyncExec() write transaction request method will result in the transactions being combined, regardless of when the invocation is made.

Associated revisions

Revision 25025
Added by Tuukka Lehtonen over 5 years ago

Make DB client combine write transactions into a single undoable operation every time WriteGraph.asyncRequest is invoked with any kind of write request.

fixes #3459

History

#1 Updated by Tuukka Lehtonen over 5 years ago

  • Description updated (diff)

#2 Updated by Tuukka Lehtonen over 5 years ago

  • Category set to DB client
  • Assignee set to Tuukka Lehtonen

#3 Updated by Tuukka Lehtonen over 5 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Applied in changeset r25025.

#4 Updated by Tuukka Lehtonen over 5 years ago

Applied in changeset r25025.

#5 Updated by Tuukka Lehtonen over 5 years ago

  • Status changed from Resolved to Closed

#6 Updated by Tuukka Lehtonen over 5 years ago

  • Story points changed from 0 to 3

Also available in: Atom PDF