-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8294361: Cleanup usages of StringBuffer in SQLOutputImpl #10320
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
8294361: Cleanup usages of StringBuffer in SQLOutputImpl #10320
Conversation
|
👋 Welcome back aturbanov! A progress list of the required criteria for merging this PR into |
|
@turbanoff The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
| BufferedReader bufReader = new BufferedReader(x); | ||
| try { | ||
| int i; | ||
| while ((i = bufReader.read()) != -1) { |
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.
Is the single character read really necessary?
BufferedReader.readLine() returns null on EOF.
It seems plausable that only the readLine and writeString are needed in the loop.
Similarly, for the read loops below for InputStreams and binary stream.
The BufferedReader and readline can be used for the binary streams by constructing with the ASCII Charset.
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.
If this single character is \n, then direct replacing with readLine would change behavior of the method.
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.
I see your point and this PR isn't the place to figure out why a single newline in the attributes Vector would be significant vs an empty string or no entry.
| BufferedReader bufReader = new BufferedReader(x); | ||
| try { | ||
| int i; | ||
| while ((i = bufReader.read()) != -1) { |
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.
I see your point and this PR isn't the place to figure out why a single newline in the attributes Vector would be significant vs an empty string or no entry.
|
@turbanoff This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 104 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
LanceAndersen
left a comment
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.
The changes seem fine based on what your goal was.
|
/integrate |
|
Going to push as commit 3419363.
Your commit was automatically rebased without conflicts. |
|
@turbanoff Pushed as commit 3419363. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
There a few unnecessary usages of StringBuffer in SQLOutputImpl class.
All of them create StringBuffer from single character and then concatenate with String. Instead of this, we can concatenate character directly.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10320/head:pull/10320$ git checkout pull/10320Update a local copy of the PR:
$ git checkout pull/10320$ git pull https://git.openjdk.org/jdk pull/10320/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10320View PR using the GUI difftool:
$ git pr show -t 10320Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10320.diff