Hi James, Sorry for the delay, I tried to get a complete overview of our issue.
So let me explain the use case. For the context, the issue was raised by a user of vert.x (http://vertx.io). This user tries to connect the vertx-jdbc-client to phoenix. A vert.x application cannot use directly the JDBC driver because it promotes an asynchronous and non-blocking development model (while jdbc interactions are blocking). The vertx-jdbc-client is using ` `prepareStatement(String sql, int autoGeneratedKeys)` which throws an exception. Actually, in the vert.x case, it would be acceptable to delegate `prepareStatement(String sql, int autoGeneratedKeys)` to `prepareStatement(String sql)`, and totally ignore the `autoGeneratedKeys`. Would this be acceptable for you (if so I would do a PR) ? Thanks and Regards, Clement On 20 novembre 2015 at 17:37:36, James Taylor ([email protected]) wrote: Hi Clement, Can you tell us a little more about your use case and how you'd like prepareStatement(String sql, int autoGeneratedKeys) to behave? Thanks, James On Fri, Nov 20, 2015 at 2:31 AM, clement escoffier <[email protected]> wrote: Hello, I’m facing an issue with the prepared statement support. Right now, we are trying a build a prepared statement using the `prepareStatement(String sql, int autoGeneratedKeys)` method. This method is not supported by the Phoenix JDBC driver. Is it something you plan to support ? Thanks & Regards, Clement
