[TBC] CLI does not support multiple SQL strings

**Bug Description**
When copying the following DDL statement, CLI has a lot of strange information output

+ sql
```sql
create table test_memory_absolute(
yumid string,
user_code string,
md5_usercode string,
cross_dp_tag string,
repeat_dp_tag string,
usercode_tail string,
insert_time timestamp,
update_time string,
city string,
city_code bigint,
cross_dp_tag_posterior string,
repeat_dp_tag_posterior string,
p_update_date int,
index(key=(user_code,update_time),ttl=0m,ttl_type=absolute),
index(key=(md5_usercode,update_time),ttl=0m,ttl_type=absolute),
index(key=(yumid,update_time),ttl=0m,ttl_type=absolute))
options(partitionnum=1,replicanum=1,storage_mode='memory'
);
create table test_ssd_absolute(
yumid string,
user_code string,
md5_usercode string,
cross_dp_tag string,
repeat_dp_tag string,
usercode_tail string,
insert_time timestamp,
update_time string,
city string,
city_code bigint,
cross_dp_tag_posterior string,
repeat_dp_tag_posterior string,
p_update_date int,
index(key=(user_code,update_time),ttl=0m,ttl_type=absolute),
index(key=(md5_usercode,update_time),ttl=0m,ttl_type=absolute),
index(key=(yumid,update_time),ttl=0m,ttl_type=absolute))
options(partitionnum=1,replicanum=1,storage_mode='ssd'
);
```

**Expected Behavior**
Prompt: create successfully

**Steps to Reproduce**

1.
2.
3.
4.

The issue shows a multi-statement SQL script causing strange output in the CLI. Look at the CLI's SQL parser and execution logic, likely in a command-line interface component. Start by reproducing the issue with the provided SQL, then examine how the CLI handles multiple CREATE TABLE statements. Check for parsing errors or output formatting bugs when processing multiple SQL strings.

Vom Indexierungsmodell aus dem Issue-Text verfasst.