Ktorm VS SQLDelight

I have been ktorm(https://www.ktorm.org) for a long time, and it suit with kotlin's stream operation very well

I mean, I'm looking at this, for example: https://github.com/kotlin-orm/ktorm/tree/master/ktorm-core/src/main/kotlin/org/ktorm/dsl, so I wonder, what would be gained from a matrix?

First google hit for "Kotlin ORM": https://github.com/kotlin-orm/ktorm

That functionality has existed for almost exactly a year

Database - SQLDelight

room is a great example but like I said our data is kotlin-only so we tend to use libraries like sqlDelight.

This seems similar to https://cashapp.github.io/sqldelight/ for kotlin, I think this approach is pretty neat, good luck with it!

Sounds like you want what SQLDelite offers, but for TypeScript. SQLDelite is only for Kotlin and SQLite though.

SQLDelight had neat built in support for this

https://cashapp.github.io/sqldelight/

You would really like sqldelight[1] then. It takes the concept of an ORM and flips it on its head. Instead of mapping function calls to SQL statements, it lets you write SQL statements and then generates classes for you that have methods for those statements.

For instance, you could have a SQL statement like getCardsForFight: select * from fights where cardId = ? and titleFight = ?, and it would generate a class that has a method getCardsForFight(cardId: number, titleFight: number).

[1]: https://github.com/cashapp/sqldelight

SqlDelight is an equivalent library in the Kotlin/JVM ecosystem that follows the same philosophy (write queries in SQL and generate code from them rather than the opposite approach taken by typical ORMs).

The only reason I haven't tested SQLDelight a lot is because they haven't implemented a way to "rename" a table when generating the classes, so if your table is called players... well, now all of the generated classes will also be named Players, which is super annoying.