Fix null pointer exception in Parser #20
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for this excellent course!
What is the issue?
When using the parser provided by the course to execute transaction commit and rollback, the Parser will first set the transaction to null, and then call the getId() method of the transaction when printing information, which will cause a null pointer exception.
What does this PR do?
Adjusting the order of codes.
How to reproduce the bug?
Start the Parser according to Lab2 2.7. Query Parser, then execute 'set transaction read only;', and then execute 'commit;' or 'rollback;'.
before fix:
after fix:
Please excuse me if I misunderstood any part of the logic.