take the bit of code on the kysely.dev front page. 4 lines of chained functions to get "select person.first_name, pet.name as pet_name from person inner join pet on pet.owner_id=person.id where person.id=1" that's nearly the simplest query one might want, and still it has to be deciphered vs read

there are escape hatches everywhere, and an easy path to writing helpers for special stuff.

same as with orms, you eventually have to break out of the limited api and perform raw sql for prrformance reasons, or for things unsupported by api, e.g. window functions.

used stored procedures extensively in production. never going back. editing requires a connection for autocompletion & errors. usually not co-located /w call sites, causing unnecessary context switches. make cicd more complex. rare readily available type-safe solutions to introspect & exec them.

if the client needs different data, version the query. Then old code using the old query still works, and new code using version 2 can be deployed at leisure const personandpet = await db .executeProcedure("getpersonandpet_1",1) if (personandpet){…}