Second datasource with jdbi

[pixnbit]

Hi, I'm having some trouble setting up a read-only 2nd datasource, with jdbi. I got some pointers and was able to put together something: I added the gradle depencencies and enabled Micronaut Data. The @Transactional and @ReadOnly("readonly") annotations work as I see TransactionalInterceptor is being called. But jdbi is not aware of the annotations, there're two jdbi instances @Named("default") and @Named("readonly") are provided by JdbiFactory. If I inject both instances into a repository, how do I make sure the correct one is picked up? My simplified setup is as follows:

// build.gradle

dependencies {
    // ...
    kapt("io.micronaut.data:micronaut-data-processor")
    implementation("io.micronaut.data:micronaut-data-jdbc")
    // ...
}

// application.yml

datasources:
  default:
    url: ${RW_URL}
    username: ${USERNAME}
    password: ${PASSWORD}
  readonly:
    url: ${RO_URL}
    username: ${USERNAME}
    password: ${PASSWORD}
    read-only: true

// UserService.kt

@Singleton
class UserService(
    private val userRepository: UserRepository,
) {

    @Transactional
    @ReadOnly("readonly")
    fun getUser(): UserEntity {
      return userRepository.getUser()
    }

}

// UserRepository.kt

@Singleton
class UserRepository(
    private val jdbi: Jdbi,
) {
    
    fun getUser(): UserEntity {
      return jdbi.withHandle<UserEntity, Exception> {
        handle.createQuery("SELECT * FROM users LIMIT 1")
                  .mapTo(UserEntity::class.java)
                  .one()
        }

    }
}

jdbi without @nAmed is always the default data source, so my current setup won't work, it's only picking up the default datasource.

[dstepanov]

In this case, you need to inject named Jdbi and use @TransactionalAdvice("myDatasource") or @ReadOnly("myDatasource") for the transactional support.

[pixnbit]

Thanks! I figured out myself for injecting the corresponding matching jdbi with @nAmed(). But I read more about the introduction AOP here. If a connection can be transaction aware, I'm thinking that if I could make the jdbi instance datasource aware with a similar AOP like the ConnectionAdvice . Please let me know if that's a good direction.