I am using the ODBC driver of TestTrack Pro (TTP) to access their proprietary database. Using MS Access and the TTP driver it works fine. So they think that there is no problem in their ODBC driver. However, when I use the jdbc-odbc bridge and call the getString function on a column which should be a memo field (in MS Access terminology) then that call does not return and the JVM starts to use all CPU time. The metadata of the ResultSet indicates that it is a LONGVARCHAR field. If the field is read using an ascii stream in a while loop then it results in the same behaviour. If the stream is used to read equal or less characters then there are characters in the field then all is well. However, the program has no way of determining the number of charaters that are present in the field. Why is the bridge not able to determine the size of the field and shouldn't it indicate that it is a CLOB?
DBTags is officially a legacy/deprecated taglib, so we won't fix this bug.