Fixed the problem that when the jdbc type is Array and Array.free() is called, the log parameter printed by BaseJdbcLogger is null.

[smagical]

#3162 Fixed the problem that when the jdbc type is Array and Array.free() is called, the log parameter printed by BaseJdbcLogger is null.

[harawata]

Thank you, @smagical .

Could you create a small demo project that reproduces the original problem you are experiencing?
I'm not sure how Array.free() is called and when it's called.
Here are some project templates and examples: https://github.com/harawata/mybatis-issues

[smagical]

demo
A very small problem, only affecting debugging

[harawata]

Thank you, @smagical ,

I understand the problem.

In the BaseJdbcLogger#setColumn() method, it seems to be better to store processed string of each parameter in columnValues instead of the object itself.
Can you think of any negative side effect?

[smagical]

This is a good idea, but I found another problem BaseJdbcLogger#getColumn() This method will cause problems. There is no way to return the original data. The same is true for my modification method, although I haven't found where yet. Call this method.

[harawata]

I'm sorry about the slow response.

You can ignore getColumn().
I'm not sure if the method used.
And java.sql.Array is rarely used anyway.

[wuyb518]

We can directly use method ps.setObject(i, parameter, Types.ARRAY);, database driver has ability to handle java array object.