CommandEvent publisher catches all exceptions

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: 4.9.0
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When I used "CommandListener", I encountered the problem of exception being caught. My scenario is that if no condition (Filter) is specified when modifying or deleting, an exception will be thrown, which is considered a dangerous operation, but in the end I threw The exception was caught by the sendCommandStartedEvent method of the ProtocolHelper class. After the capture, it was not thrown again, causing my program to continue executing and all collection data to be deleted. Is there any way to bypass the capture, or is there anything else? The method allows me to obtain it before the statement is executed, such as the interceptor in MyBatis

              Assignee:
              Slav Babanin
              Reporter:
              chaoyang jia
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: