Is trying to use `sqldelight` in ktor server a bad...

# ktor

[ursus]

Is trying to use sqldelight in ktor server a bad idea? I'm already familiar with it but I'm unsure about the schema creation, ddl etc, since sqldelight seems to be driven by the DDL - which from what I gather is not used in backend apps? (I'm a android developer, backend noob)

[madisp]

we are using sqldelight with postgres in the backend, IMHO it's not a bad idea at all

[madisp]

there's also jOOQ which is also based off sql afaik?

[madisp]

also, when using jdbc make sure all queries are on a separate thread pool from the call handlers

[ursus]

do you use flyway or does sqldelight create and mkgrate db?

[madisp]

we use sqldelight migrations, but in hindsight probably should try out flyway at some point

[ursus]

do you do hikari?

[madisp]

yup

[ursus]

anything else special I'd need to know? (im android dev just starting with ktor)

[madisp]

I think there's also an async postgres driver, but we haven't checked that out yet

[ursus]

are you on java 21+?

[madisp]

yup, I think currently on 21 LTS and switching to 24 soonish to move some of the io workload onto virt threads

[ursus]

aren virt threads on in 21 already?

[madisp]

24 has some improvements w.r.t pinning - synchronized stuff no longer pins the threads

[madisp]

btw, my background is really similar - I did a ton of Android stuff before starting this project

[ursus]

yea ktor is easy for me to pickup but the db
i already know sqldelight, but I was told in "proper" backends, flyway managers db migration,and is run by a standalone jar before the server starts