CLI with interactive=false does not print error message if fail to execute SQL

Now we use `interactive=false` to execute SQL and it does not print any error message if we pass the incorrect SQL.

BTW, the SQL should be end with `;` which is not expected.

Look at the CLI code that handles SQL execution with interactive=false. The issue mentions that error messages are not printed when SQL is incorrect and that SQL should end with a semicolon. Start by finding where SQL commands are parsed and executed in non-interactive mode, then add error output. Check if there are existing tests for CLI error handling to verify the fix.

Escrito por el modelo de indexación a partir del texto del issue.