datafusion-cli support for multiple commands in a single line

[berkaysynnada]

Which issue does this PR close?

Closes #.

Rationale for this change

While we can write CLI commands sequentially such as:

CREATE TABLE test1 (
    c1 VARCHAR(255),
    c2 INT,
    c3 INT
);

INSERT INTO test1 (c1, c2, c3) VALUES ('c', 2, 1);

SELECT * FROM test1;

CLI gives error to write more commands after "CREATE EXTERNAL TABLE":

CREATE EXTERNAL TABLE test1 (
    c1 VARCHAR(255),
    c2 INT,
    c3 INT,
    ...
)
STORED AS CSV
WITH HEADER ROW
LOCATION '/Users/berkaysahin/Desktop/datafusion-upstream/testing/data/csv/aggregate_test_100.csv';

SELECT * FROM test1;

🤔 Invalid statement: sql parser error: Expected end of statement, found: SELECT

What changes are included in this PR?

This PR addresses the issue that we needed to enter commands one by one for creating external tables. It resolves this by splitting the entire string at semicolons, ensuring each segment passes parser checks one by one, and then executing them sequentially.

Are these changes tested?

Are there any user-facing changes?

[mustafasrepo]

LGTM!. I wonder though how we can test this support in the code base.

[alamb]

this is a nice change -- thank you @berkaysynnada

[alamb]

You can probably avoid a copy here if you passed in a reference

Suggested change

	pub(crate) fn split_from_semicolon(sql: String) -> Vec<String> {
	pub(crate) fn split_from_semicolon(sql: &str) -> Vec<&str> {

[berkaysynnada]

I cannot find a copy here. If pass the reference, I also need to copy it for exec_and_print().

[comphead]

We may want to add a test? Just wondering if it will work for query

select ';'

?

[berkaysynnada]

I will send a commit excluding semicolons if they are in "" or '', and some tests.

[alamb]

Looks like an improvement to me. Thanks @berkaysynnada

[alamb]

👍 thank you for the tests 👍

[alamb]

This is likely pretty brittle (likely won't handle all crazy corner cases, like for example when there are escaped quotes \\', but I think it is better than what we have now.

Thanks @berkaysynnada