-
Notifications
You must be signed in to change notification settings - Fork 311
Prevent crash in SQL Server's JDBC when tracing execute methods with generated keys #9321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
na-ji
wants to merge
4
commits into
master
Choose a base branch
from
naji.astier/sqlserver-jdbc-generated-keys-workaround
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+32
−3
Open
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
69211ed
Prevent crash in SQL Server JDBC when tracing execute methods with ge…
na-ji 94d3981
remove dynamic typing when packing all the JDBC arguments
na-ji e84d9eb
move JDBC test on injection with generated keys to SQL Server file
na-ji 3a324e0
remove useless constant in StatementAdvice
na-ji File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Advice should not depend on the instrumentation class, because the advice bytecode will be lifted and injtected into the class that lives in the application class-loader. This happens to work here because
StatementInstrumentation.appendComment
is a constant which gets inlined byjavac
, but we should not rely on this. If someone ever changedStatementInstrumentation.appendComment
to not be a constant then this advice would break and users would lose JDBC traces.Can you remove
StatementInstrumentation.appendComment
from the surrounding class and replace its use here by the literal valuefalse
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be fair, I don't really understand why we have this constant on this class. It used to be used here, and but its type was final static so it wasn't really useful.