[Springframework-developer] SqlQuery.execute() untyped parameter Object[]

[David S. <ds...@mi...>]

Hello... I hope it's appropriate to post my comment to this list since
it's not a usage assistance issue (in which case I'd be sending this to 
the user list).

I just started working on project here that uses Spring jdbc.core's
JdbcTemplate & the gang in that package. When I discovered the higher 
order abstractions in jdbc.object, it seemed to me that we should use 
those facilities. The lead developer of the project told me that he 
deliberately avoided it because he thought the *untyped* Object[] array 
to parameterize a query as found in SqlQuery.execute() was a very poor 
design choice. He preferred the interface and use of 
PreparedStatementSetter as used within jdbc.core. I tend to agree but I
still want to use the package anyway. I do see the declareParameter() 
and setTypes() methods of RdbmsOperation but this just separates the 
type determination from specifying the parameter values when it could be 
done at once (again, as with PreparedStatementSetter). Can the rationale 
between the Object[] parameterization in jdbc.object be explained, and 
perhaps could jdbc.object be reworked in the future to handle a 
PreparedStatementSetter or some similar typed parameter strategy?

Thanks.

~ David Smiley
MITRE