Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • None
    • None

    Description

      PHOENIX-5709 skips generating index delete mutations if the data table rows (and thus the index table rows) do not exist. However, it allows the delete mutations to be applied on the data table. This does not create a data integrity problem but creates an extra case to handle for the inline verification implementation to consider. PHOENIX-5709 currently does not handle this case. We should either apply these delete statements to both tables or apply none of them.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            kozdemir Kadir OZDEMIR
            kozdemir Kadir OZDEMIR
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 40m
                40m

                Slack

                  Issue deployment