Commit failure is silently ignored during history synchronization

XMLWordPrintable

    • Sprint 23, Sprint 24, Sprint 25
    • 0.5

      DBcommit no longer set transaction error, so if it fails then it will not be detected and cache will be updated during history synchronization while database will not have the changes.

      This can lead to a problems such as trigger being stuck in one state, and missing notifications, though it's possibly a corner case that all other queries succeed but only commit fails.

            Assignee:
            Vjaceslavs Bogdanovs
            Reporter:
            Vladislavs Sokurenko
            Team C
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: