In sql templates, if you get the bind param name wrong, it puts out a VERY cryptic error that it can't resolve a data type

Any

....!

@Toshihiro Nakamura Is there a way to use the QueryDsl to generate an sql statement and get it's parameters (w/o initializing a connection to a db)? It would be a great way to migrate code using a low-level library such as Jyasync to Komapper... one could just write the entities, and sqls little by little using the dsl, but running them using jasync, and when all the queries are migrated, then just update the jasync wrapper to use komapper's runQuery.

Oh.. it looks like there's dryRun() 👍🏼 !

The only problem is that there's no way to provide a dialect w/o a real connection?

It seems like

Row::getNotNull

doesn't return fields that are supposed to be wrapped in a

value class

in fromTemplate... I wonder if there's any way to make it wrap the value when a value class is needed...? It would make this more consistent with the behaviour for value classes elsewhere...

Maybe by having a ValueClassDataType?

I smell a new version coming soon (two nice features already committed to master...)?

Just wondering @Toshihiro Nakamura, maybe since we already got so far having aggregate roots and relationship annotations, could it be feasible to generate

EntityStore

subclasses for each aggregate root, and have it store the the root by itself type safely and the relations already in the form they need to be?

Hi, everyone. Komapper v1.7.0 has been released. This version includes an experimental feature, the Association API. Please try it out. https://github.com/komapper/komapper/releases/tag/v1.7.0 https://www.komapper.org/docs/reference/association/

Happy to see the association API now available, and was the last thing keeping me from switching in my project. One suggestion I have. When context receivers are enabled it would be even better if the generated methods were getters, and removed the need for parenthesis

I enabled context receivers functionality in my project but the generated code doesnt compile It generates this:

@org.komapper.annotation.KomapperExperimentalAssociation
context(org.komapper.core.dsl.query.EntityStoreContext)
fun zt.minkinator.data.Guild2.`markovConfig2`(

Which doesn't compile because

context

has to be above annotations

Expecting a top level declaration

i noticed that running a query isnt a suspend function, any specific reasons why komapper isnt using coroutines?

What if in

withTransaction

blocks, it passed the database as the

this

scope?

Is there a way to do a clean shutdown of an R2dbc connection pool that was was passed as a

ConnectionFactory

in

R2dbcDatabase(...)

? Like when shutting down a Ktor server in Kubernetes, will all the connections be closed automatically? Otherwise, I'd need some kind of

close()

to clean them up on

SIGTERM

or

SIGINT

.

What does wrapping my queries within with transaction do exactly? I'm not very familiar with how databases work

Hi, everyone. Komapper v1.8.0 has been released. Please try it out. https://github.com/komapper/komapper/releases/tag/v1.8.0 We have opened an Open Collective account. If you use Komapper in your project or enterprise and would like to support ongoing development, please consider becoming a backer or a sponsor. https://opencollective.com/komapper

I'm using 1.8.0 and making use of the association API. I was wondering how can I make my entity have a default value for an assocation?

@KomapperEntity
@KomapperAggregateRoot("guilds")
@KomapperOneToOne(targetEntity = MarkovConfig::class)
@KomapperOneToMany(targetEntity = Filter::class, navigator = "filters")
data class Guild(
    @KomapperId
    val id: Long,
    val markovConfigId: Int,
    @KomapperColumn(alternateType = ClobString::class)
    val data: String = ""
)

@KomapperEntity
@KomapperOneToOne(targetEntity = Guild::class)
data class MarkovConfig(
    @KomapperId
    val id: Int = 0,
    val enabled: Boolean = true,
    val frequency: Float = 0.5f,
    val handleMention: Boolean = true
)

When creating the Guild entity, I would like to only have to specify the id, with a default MarkovConfig entity associated, is this possible? Any other advice on my code would be appreciated

I'd suppose it's not possible to use a DataTypeConverter to map a field type to a sealed class instance based on two fields in the database?

Is there a way to add a field to an entity that's lazy? Meaning I don't want it loaded unless I ask for it in a select... @Toshihiro Nakamura

Is there some way to shut down the database connection gracefully when my program receives the shutdown signal?

We have prepared a Contribution Guide on Komapper documentation. Please send us a Pull Request if you find any improvements in the documentation. https://github.com/komapper/komapper-docs/blob/main/CONTRIBUTING.md

Hi, everyone. Komapper v1.9.0 has been released. Please try it out. https://github.com/komapper/komapper/releases/tag/v1.9.0

Hello. We have the plan to support

INSERT ... RETURNING

feature. Any suggestions are welcome. https://github.com/komapper/komapper/pull/962

Hello! I can see in the README.md that R2DBC + SQL Server is currently unstable. Is there a roadmap/plan to make this stable?

Hi, everyone. Komapper v1.10.0 has been released! This version supports INSERT...RETURNING and UPDATE...RETURNING. You can execute your queries more efficiently than before. Try it out. https://github.com/komapper/komapper/releases/tag/v1.10.0

How can I have a default value for an associated entity? I have this Guild entity, that I want it to have a default config

@KomapperEntity
@KomapperAggregateRoot("guilds")
@KomapperOneToOne(targetEntity = MarkovConfig::class)
@KomapperOneToMany(targetEntity = Filter::class, navigator = "filters")
@KomapperOneToMany(targetEntity = DBMessage::class, navigator = "messages")
data class Guild(
    @KomapperId
    @KomapperColumn("GUILD_ID")
    val id: Snowflake
)

@KomapperEntity
@KomapperOneToOne(targetEntity = Guild::class)
data class MarkovConfig(
    @KomapperId
    val id: Int = 0,
    val guildId: Snowflake,
    val enabled: Boolean = true,
    val frequency: Float = 0.5f,
    val handleMention: Boolean = true
)

Hi, a question about komapper, I have 2 tables with an association table :

User(id: Int), Game(id: Int), UserGame(gameId: Int, userId: Int)

I want to use the association API to be able to do like

users.games()

and

game.members()

, but I don't quite understand the docs about this How can I do this ? I currently only created two data classes for my 2 tables, but none for the association table.

How could I simplify my code by using interfaces (or maybe sealed interfaces if needed) ? I have a bunch of data classes that also are komapper tables, and I want to generate a few shortcut methods on each class, so I can just do

User(username = "", password = "").insert()

I don't know if it's a good thing to do, stop me if I'm wrong ! But I can't find any way to get the

QueryDSL.insert()

method work, it always says that I'm having the wrong type, even when getting the metamodel by reflection or by a property in my interface, I don't quite get it Could you help me figuring all this ?

Hi, little question, can I use a

kotlinx.datetime.Instant

for a

@KomapperCreatedAt

field ?

Also, should I use JDBC or R2DBC, what is the difference and what should one use today and why ? It's for MariaDB