Skip to content

Fix typo in multi-statement announcement comment #671

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.

Sign up for GitHub

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
kazanzhy wants to merge 3 commits into
base: trunk
Choose a base branch
from
+3 −3
Open

Fix typo in multi-statement announcement comment #671

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
97d83bf
Fix typo in multi-statement announcement comment
kazanzhy Jun 15, 2026
c7c5285
Fix typo in SERVER_MORE_RESULTS_EXISTS comment
kazanzhy Jun 16, 2026
62005de
Change COM_SET_OPTION type from 0x1A to 0x1B
kazanzhy Jun 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions sql/protocol_classic.cc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -270,7 +270,7 @@
07 00 00 0b 00 01 00 02 00 00 00 ...........
~~~~~~~~~~~~~

If the ::SERVER_MORE_RESULTS_EXISTS flag ise set, that indicates more
If the ::SERVER_MORE_RESULTS_EXISTS flag is set, that indicates more
resultsets will follow.

The trailing @ref page_protocol_basic_ok_packet is the response to the
Expand Down Expand Up @@ -309,7 +309,7 @@
A multi-statement is permitting ::COM_QUERY to send more than one query to
the server, separated by `;` characters.

The client musst announce that it wants multi-statements by either setting
The client must announce that it wants multi-statements by either setting
the ::CLIENT_MULTI_STATEMENTS capability or by using
@ref page_protocol_com_set_option
*/
Expand Down