Could you explain how you're using prepared statements for DDL statements? Are you parameterizing parts of the DDL statements with question marks to be filled in by the PreparedStatement parameters?
On Tue, Mar 31, 2015 at 3:48 AM Nick Dimiduk <ndimi...@gmail.com> wrote: > Working on PHOENIX-971, I'm wondering what the expected behavior should be > for PreparedStatements created from CREATE TABLE sql with parameters. > Calcite's Avatica depends on the statement to identify the parameter types > at compile time, and return meaningful values for method invocations on > ParameterMetaData. It looks like Phoenix's CreateTableCompiler is > recognizing the number of parameters in my sql, but is not inferring type > information. > > My question is: should Avatica be more flexible in allowing "fuzzy" > signatures for PreparedStatements, or should Phoenix's > StatementPlan#compile methods be determining parameter types in all cases? > > Thanks, > Nick >
