A modern programming language that makes developers happier.

kotlinlang

Hey, I’m trying out adding Komapper to an existing project and ran into an issue with spring boot auto configuration with r2dbc connection pooling. Since the configured connection string we have is something like: `r2dbc:pool:<postgresql://localhost>:port` , from what I’ve gathered komapper will detect the SQL dialect as “pool” and fail to configure the database connection. Are you aware of this issue?

I don't know to tell you if this is a bug, but you can specify the dialect yourself if need be as a workaround.

Thank you for the report. We will fix the issue in the next version. As a workaround, please define the following Bean in your application.
```@Bean
fun dialect(): R2dbcDialect {
    return PostgreSqlR2dbcDialect()
}```

Thank you! Using the workaround works great for us

<@U05RA7MLZT2> We have fixed this issue in Komapper v2.1.0. Please give it a try.
<https://github.com/komapper/komapper/releases/tag/v2.1.0>

Thank you very much, I can confirm it works as expected