Ktorm VS SQLDelight

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

SQLDelight + Kotlin is a match made in heaven. Plus it's much nicer than having to mess with any ORM 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.

Something I'll add because it hasn't been mentioned yet is sqldelight.

Some Libraries That Work Really Well SQLDelight as the name implies, this library is for dealing with SQL on all platforms that KMM supports. It's somewhat easy to use and works extremely reliable, plus has a very active community.

Persistence: Room, SqlDelight

Now if you're just writing a crud app (what my hobby project is) and you use compose multiplatform for your UI, SQLDelight for persistence, and one of the many MPP architecture libraries, you don't have to write a wrapper.

I did not know about SQLDelight! Thanks for sharing that. I just took a quick look at it. From what I saw, it might not work for my use case. But I'm not 100% sure unless I spend a few hours actually trying it out. I'm building a library where the database tables are already defined by the system. I'm talking about the Contacts Provider. Let me know if you think that it's possible. Otherwise, I'll give it a try when I miraculously get some free time lol.

may i suggest instead: SQLDelight