When fetching varchar type data from SQL engine, mxosrvr will apply for enough memory to ensure that the data can be stored, regardless of the actual varchar length.Then send such a large piece of data to jdbct 4.This results in unnecessary network overhead and JDBC memory usage.
So I added a function to clip the resulting data. The data to be sent to JDBCT4 in mxosrvr is trimmed to reduce network overhead and memory consumption.This function cuts out the redundant parts of varchar type data, and is very useful for the case where varchar is very long but actually occupies very little.
I added a switch to jdbct4 code to turn this function on and off according to the situation.
I tested my code with phx