Skip to main content

Search

Welcome to Tibero GTS!

JDBC-590704 Error Occurs When Using Cursor During iBatis/Mybatis-Tibero Integration

Document Type | Troubleshooting

Category | App Development

Applicable Product Versions | 6FS01, 6FS02, 6FS03, 6FS04, 6FS05, 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02, 7FS02PS

Document Number | TDETI002

 

Issue

When using Cursor during integration of iBatis, Mybatisโ€”which are Object Relation Mapping (ORM) frameworks that facilitate interaction between the database and JAVA applicationโ€”and Tibero, a JDBC-590704: Unsupported SQL Type error occurs.
Note
An error occurs during type parsing when declaring jdbcType="CURSOR" in the mapper definition section within iBatis/Mybatis, and third-party solutions using iBatis/Mybatis may also be affected.
 
 
 
 

Cause

This phenomenon occurs due to differences in JDBC mappers when integrating iBatis/Mybatis.
 
In ibatis/mybatis, the JdbcType enum is set based on Oracle standards by default, where the Cursor value is declared as -10; however, in Tibero JDBC, the Cursor value is defined as -17, which causes this issue.
 
 
 
 

Solutions

  1. Add the constant value TB_CURSOR(-17) to org.apache.ibatis.type.JdbcType.java in MyBatis and build
  2. Generate the jar file
Note
For additional inquiries regarding the procedure such as specifying jdbcType="TB_CURSOR",
please contact Tmax Tibero Technical Support (1544-8629).
 
 
 
 
 
 
 
 

Related to