Instead of suppressing CAST at getExplainer, do it in the formatter, but not if VERBOSE.
Rearrange how plans are formatted a little to make toString() shorter and rules test output a bit more verbose.
Update test expected results.
Add a test option to show the types for the paramters, which is one of the important jobs of the types resolver rule.
Add a test demonstrating the problem.
Add an assertion against parameters not having their type determined.
Add type from explicit cast into the parameters sync.
Now get expected result.
Add an assertion against unknown parameters getting in.
Pick up any parameters to EXPLAIN or PREPARE when called from PSQL.
Add a test for the problem of parameters with no obvious type.
It's too late to handle those at assembly time. Move up with other parameter type finalization.
LIMIT ? needs to set type to INT.
Don't try to make expressions of result columns we don't need.
Add a test to check random param indexes.
Set a default type back into preptime value for constant folder.
Skip over missing parameters (only higher ones given by number).
merge MMcM: Some changes to logging of casts and parameters

Merge pull request #1188 from MMcM/sql-layer/verbose-casts-and-log-params
https://github.com/FoundationDB/sql-layer/pull/1188
merge MMcM: Fix a number of problems with parameter types

Merge pull request #1189 from MMcM/sql-layer/sql-param-types
https://github.com/FoundationDB/sql-layer/pull/1189
Add a call to function via JDBC syntax (which is recognized by our parser).