Bug #7685

DB client state gets corrupted when removing persistent statement inside a virtual write

Added by Antti Villberg 4 months ago. Updated 2 months ago.

Status:ClosedStart date:2017-12-16
Priority:4Due date:2017-12-21
Assignee:Antti Villberg% Done:

100%

Category:-Spent time:-
Target version:2018-02
Release notes:Fixed DB client state handling bug when trying to remove a persistent statement inside a virtual write request.
Tags: db, 1.32.0, corruption
Story points-
Velocity based estimate-
ReleaseSimantics 1.32.0Release relationshipAuto

Related issues

Related to Platform - Bug #7686: Disable forced model activation after migration Closed 2017-12-07 2017-12-21

Associated revisions

Revision 60887e49
Added by Antti Villberg 4 months ago

DB client state gets corrupted

refs #7685

Change-Id: Ic6a8b7f2f9e327c8aba774a86f834d160a9c4c66

History

#1 Updated by Tuukka Lehtonen 3 months ago

  • Tags set to db, corruption, 1.31.0
  • Status changed from New to Feedback
  • Assignee set to Antti Villberg
  • % Done changed from 0 to 100
  • Release set to 56
  • Release notes set to Fixed DB client state handling bug when trying to remove a persistent statement inside a virtual write request.

#2 Updated by Tuukka Lehtonen 3 months ago

  • Tags changed from db, corruption, 1.31.0 to db, corruption, 1.32.0
  • Release changed from 56 to 57

#3 Updated by Tuukka Lehtonen 3 months ago

  • Target version changed from 2017-28 to 2018-01

#4 Updated by Tuukka Lehtonen 3 months ago

  • Target version changed from 2018-01 to 2018-02

#5 Updated by Tuukka Lehtonen 2 months ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF