A modern programming language that makes developers happier.

kotlinlang

Hey, just a question in regards to SQLDelight: is it intended that there are no interfaces anymore for the queries?

<@U01JRLZH77T> can you maybe share the reasoning behind it?

We don’t see a use case. For production you use the classes directly, there is a 1:1 relation to the implementation class.
If your use case is testing, instead of mocking some queries only you should mock the repository.

Thank you for your explanation.

Indeed my concern goes more into tests. I know what you intentions are, however I would have loved to keep the decision of the test tactics to the implementers. This goes especially for KMP.
Would you be open to a contribution to reintroduce that capability?

I am open yes, but before opening a PR, create an issue first to discuss it. 

are you trying to avoid using an in-memory database in tests?

Not all dialects/dbms supports an in memory db, the db2 docker container takes 5-10 minutes to start too, so avoiding that time would be a nice use case. 