I've started running an avatica server with JdbcMeta against a larger set of queries. This has enlightened me of the semantics of JDBC's different execute methods. It seems our RPC interfaces do not expose enough information to be able to pass these semantics between client and server. For instance, CREATE TABLE and UPSERT statements are not accepted.
My question is whether we should extend the RPC protocol to follow JDBC spec (execute, executeQuery, executeUpdate) or add parameters to our single method. I'm comfortable with the short-term decision (more RPC boilerplate vs switching logic on client and server) but I'm wondering if there are longer-term consequences I should consider; I'm not terribly familiar with JDBC, nor how it differs from ODBC, &c. Any advice is appreciated. Thanks, Nick
