Software Environment:
OpenLooKeng version (source or binary): NA

OS platform & distribution (eg., Linux Ubuntu 16.04): NA

Java version:

Describe the current behavior
when executing SQL statement(select/insert/delete/update) with ODBC API, the default process of openLooKeng driver is executing MySQL c/s binary message with openLooKeng server, that is COM_PREPARE + COM_EXECUTE. As we use gateway to act as a server agent and gatewat is written in JAVA with JDBC, COM_PREPARE is then devided into 5 message exchange stages with openLooKeng server.(the stages are as below: prepare statement + describe input statementId + describe output statementId + deallocate statementId).
These are very heavy call process, and performance will be delayed heavily in low network env(gateway<--->openLooKeng server). Network workload is also heavy in this work mode.

Describe the expected behavior
When executing SQLstatements with no input parameters, driver sends COM_QUERY message instead of COM_PREPARE+COM_EXECUTE, in this way gateway need only one JDBC cmd exchange with openLooKeng server.
We can observe the difference with openLooKeng server's web page in which shows commands.

Steps to reproduce the issue
same as expected behavior

Related log/screenshots
NA

Special notes for this issue
NA