mybatis | mybatis源码中文注释

You are hitting the limitation of Java here so the is no elegant solution to this without the help of a 3rd party library (which is still great and I highly recommend).

Use constructor injection and not property injection in result maps and also use lombok to automatically generate constructors for you (and/or lombok's @NonNull checks if you use Boolean).

So if you have class:

A SqlSessionFactory will use the transaction manager associated with the Datasource. MyBatis is using Spring's native transaction management so you can configure Datasources and transaction managers as is normal in Spring. The trick is to create multiple SqlSessionFactories and associate mappers to them.

The basic idea is to make two SqlSessionFactories and give them different names:

From that same documentation page - you can register a package and all interfaces in the package will be registered. This is far less verbose than registering mappers individually:

The mapper class needs to be a valid Java class name. Change your mybatis-config.xml to the following:

Yes, it will once it reaches GA.
'M1' means it still is a milestone release.
See this answer for the details.

this is caused by too old spring-boot-gradle-plugin. It is using property which was removed in Gradle 7. I'm checking the history and you would probably need at least version 2.2.2.RELEASE.

I believe the fix has been done as part of Gradle 6 compatibility (see Release Notes)

I haven't tested that 2.2.2.RELEASE will fix that for sure just guessing based on code changes in the plugin. We are on 2.3.x and that works.

Having two separate interfaces one for repository and another for mybatis mapper is just how mybatis integration in spring-data-jdbc works as of now (version 2.2.1).

Mapper is just an implemenation detail of the spring data repository and just should not be used by the clients, so it should not be an issue.

What you want can be probably done but will require quite some work and might not be worth it.

@Repository annotation instructs spring-data-jdbc to create a proxy implementing PersonRepository with all the machinery of fetching/saving objects to the database.

@Mapper on the other hand instructs mybatis-spring to create another proxy that will handle queries from the mapping provided in xml or via annotations on the interface method.

Only one of this proxies can be injected in the places where you are going to use PersonRepository. What you can do is to create your own proxy for PersonRepository that will create both spring-data-jdbc and mybatis proxy and will dispatch calls to them. But the complexity of this solution will be rather high compared to a simple class that delegates to two separate PersonRepository and PersonMapper.

Update: it seems there is a way to combine mybatis mapper with repository as described in this comment https://github.com/spring-projects/spring-data-jdbc/pull/152#issuecomment-660151636

This approach uses repository fragments to add mybatis fragment to the repository implementation.

Unfortunately, there is no way to specify a current schema for the session. In InterSystems products supposed to use schema names all the time in all queries. And default schema for the whole system can be changed in settings.

I solved my issue by creating an XML mapper that defined a collection property in the result map:

SiteScheduleMapper.xml