PreparedStatement_setArgs(p, 's', "a string", 'i', 42, 'f', 3.1415926);
 the number of parameters is assumed equal to the number of '?' in the query. i also have something similar for reading results from the ResultSet, but that required pointers and a count, and was much more likely to lead to errors.
> have you considered a varargs call for setting parameters with type codes?
one more thing that i assume must work this way, but you don't seem to have documented, is how to test for exceptions. i guess SQL_Exception (a return value, right?) is false when there's no error?
related: do you have any examples that include all the error handling that would be necessary in a real app? how do you display the exception details (it seems to be an opaque type) to the user? perhaps i am missing something here (can't even find exception in the clickable API image)?
(wish i had known about this a few months ago as it would have saved me some work - thanks).