How to deal with the pits encountered by the text type in the code of automatic generation of Spring and MyBatis integration

This article will explain in detail how to deal with the pits encountered in the automatic generation code of Spring and MyBatis integration. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

After the integration of Spring and MyBatis, the dao and mapper configuration files are generated using the automatic code generation tool, as follows (take Intelli idea as an example).

1. Write and generate the code configuration file generatorConfig.xml.

two。 Configure the following maven to run the command.

3. Just run generatorcode.

Problem description

If there are text or blob fields in the database table. The automatically generated database configuration file is as follows, with several more methods and resultMap ending in withBlobs:

Select distinct, from edu_website_profile order by ${orderByClause}

If selectByExample or updateByExample is still used for querying or updating data at this time, the resulting text or blob data is null.

Correct approach

You should use either selectByExampleWithBLOBs or updateByExampleWithBLOBs.

On "Spring and MyBatis integration automatic generation code in the text type how to deal with the hole" this article shares here, I hope the above content can be of some help to you, so that you can learn more knowledge, if you think the article is good, please share it out for more people to see.