This was a problem in questdb-connect version 1.1.2 and older versions. questdb-connect 1.1.3 now supports the VARCHAR type, so workarounds are no longer needed.