Firebird clobs incompatible with mybatis 3.4.x

[sinforosoft]

MyBatis version

3.4.x
I have checked that MyBatis version 3.3.x works without any problem.

Database vendor and version

Firebird 2.5.7 with Jaybird 2.2.12 JDBC driver.
Other Firebird/Jaybird combinations have been tested, all of them with the same result.

Steps to reproduce

Any select on a firebird table including a clob (blob sub_type text) field, will throw an ResultMapException, due to unsupported java.sql.Clob.length method.

Expected result

As java.sql.Clob.length is not a required JDBC method, mybatis should fallback to other (required) methods when length() is not supported by the JDBC driver. See http://tracker.firebirdsql.org/browse/JDBC-270

Actual result

org.apache.ibatis.executor.result.ResultMapException: Error attempting to get column 'DIRECCION' from result set. Cause: org.firebirdsql.jdbc.FBDriverNotCapableException: Not yet implemented.

[harawata]

In 3.3.x, StringTypeHandler was used.
In 3.4.x, ClobTypeHandler is used due to an improvement (#248).

You just need to tell MyBatis to use StringTypeHandler for LONGVARCHAR (or CLOB) columns.

<typeHandlers>
  <typeHandler jdbcType="LONGVARCHAR"
      javaType="string"
      handler="org.apache.ibatis.type.StringTypeHandler" />
  <typeHandler jdbcType="CLOB"
      javaType="string"
      handler="org.apache.ibatis.type.StringTypeHandler" />
</typeHandlers>

[sinforosoft]

I can confirm this workaround fixes the problem.

[kazuki43zoo]

@sinforosoft Thanks for confirming !
@harawata I think better it write in release note of 3.4.0. WDYT ?

[harawata]

@sinforosoft Thanks!
@kazuki43zoo Sure!