How to solve the problem of Mybatis Generator mapping tinyint to Byte and Boolean
Editor to share with you how to solve the problem of Mybatis Generator mapping tinyint to Byte and Boolean, I believe most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!
1. For tinyint (4) to map to a Byte1.1 environment
Spring boot 2.1.x
Mybatis
Tk.mybatis
Mysql
1.2 Custom type parser
(1) create the following classes
Public class CustomerJavaTypeResolver extends JavaTypeResolverDefaultImpl {public CustomerJavaTypeResolver () {super (); / / Map the TINYINT of the database to Integer super.typeMap.put (Types.TINYINT, new JavaTypeResolverDefaultImpl.JdbcTypeInformation ("TINYINT", new FullyQualifiedJavaType (Integer.class.getName ();}}
(2) add to pom.xml
Org.mybatis.generator mybatis-generator-maven-plugin 1.3.6 mysql mysql-connector-java 5.1.29 Com.taco.cloud-generator-core 1.0-SNAPSHOT tk.mybatis mapper 4.1.5 True true src/main/resources/mybatis-generator.xml
(3) modify the mybatis-generator.xml file and add
two。 Solution for the case where tinyint (1) is mapped to Boolean
The tinyInt1isBit=false parameter is added to the URL of JDBC. Note that the parameter name is case sensitive, otherwise it will not take effect.
For example: jdbc:mysql://$ {ucmha.proxy1_2.host} / ${db.mysql.db}? tinyInt1isBit=false
Replace with tinyint (2)
These are all the contents of this article entitled "how to solve the problem of Mybatis Generator mapping tinyint to Byte and Boolean". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!
