Fix and extend tests to exercise all code paths -- varchar over and under the threshold and varbinary.
Also test inline and non-inline sizes for both types.
Also, test UPDATEs, just for completeness.
Also test with an ad hoc query -- use "||" on the value to fool the planner into allowing a long string.
Also test with a user-defined stored proc that checks the success of the executeSQL and tries to access the error message
and simply returns some kind of user-defined error code to the client.
Also test with a user-defined stored proc that just tries to return the result from executeSQL to make sure that the error message gets back to the client.
In retrospect, I think we should have sized this ticket larger than 1.