Hello, Roman,

>> I appreciate your prompt response. Would you know how long it takes
>> for a fix to be put out so that we can download and use it?

> Engine developers mean that this is "as designed". This means that fix
> will not be available soon. There are possible workarounds:

> - declare column as VARCHAR(2) from the very beginning;
> - declare column as CHAR(2) CHARACTER SET OCTETS (or any other
> one-byte charset);

You did not answer my question. What happens if you ask engine to
translate XSQLVAR type to SQL_VARYING explicitly for CHAR output
parameters ? Is it still coming padded ? If no, this can be a nice
solution for Jaybird users. If yes, then it can be easily fixed
in database server itself.

> Roman Rokytskyy

Nickolay Samofatov