feat: support multiline SQL input in obclient #<573> #604
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.
What problem were solved in this pull request?
Previously, obclient did not support multi-line SQL input.
When users entered a statement that spanned multiple lines (e.g., CREATE TABLE), the client failed to parse it and returned an error.
Issue Number: close #573
What is changed and how it works?
Enhanced the client input handling logic to buffer input until a terminating semicolon (;) is received.
Modified the prompt to match MySQL-style continuation (->) for multi-line queries.
Now, users can input SQL statements across multiple lines, and the client will execute them only when complete.
Example before:
miniob > create table t(
SQL_SYNTAX > Failed to parse sql
Example after:
miniob > create table t(
-> a int,
-> b int);
SUCCESS
Other information
Tested with CREATE TABLE both single-line and multi-line.