Uploaded image for project: 'Tech Debt'
  1. Tech Debt
  2. DEBT-1

No optimistic locking/update conflict resolution

    XMLWordPrintable

    Details

    • Template:

      Description

      Reliability of the system, data consistency

      How to handle concurrent (conflicting) updates to records?

      UXPROD-1752 not in MVP List (row 499). Lobby for this to be included in Q1 or Q2 of 2020. It's important but may not outweigh other functional features/work. May implement as a "client opt-in" manner.

      Update July 17 2019: No activity to date. Discussion about deprioritizing since some have indicated it's not abnormal or not a big problem. Others, though, feel it's an expectation when coming from a traditional client-server SQL-based solution. Decided to leave a 'High' for several reasons.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jakub Jakub Skoczen
              Reporter:
              zburke Zak_Burke
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: