"generateAsync = true" doesn't work

[armond-avanes]

When I enable async in the database definition in my build file, I can't get my code compiled because an async version of Database.schema is generated and SQLiteMCDriver.Factory(...) doesn't accept any such schema.

sqliteMC {
    databases {
        create("Database") {
            packageName.set("com.my.package.name")
            generateAsync = true
        }
    }
}

[05nelsonm]

Will have to add. PRs welcome!

I am curious about your setup, though. Do you have JS targets for your project?

The only reason for using generateAsync = true is if you have JS source sets, which this repository does not support. For non-js, the async schema simply calls the non-async functions under the hood with no context switching to execute on a BG thread. There is no benefit to using it for non-js, as you'd still have to wrap all calls (suspending or not) in withContext blocks, providing it your desired dispatcher.

[armond-avanes]

@05nelsonm I don't have any JS/Web target in my project.

What I'm trying to achieve here is to get coroutine support (suspend functions) for insert, update and delete statements (plus transactions). With the current support for flows, I could only apply it to my queries. I thought generateAsync = true could do it.

Please let me know if I'm missing anything here and the support is already there for having suspend insert/update/delete/transaction statements.

[05nelsonm]

So the generateAsync functionality is only there to support JS. For non-js targets, those generated suspend functions will call the underlying blocking (non-suspending) functions. The suspend functions do NOT switch dispatchers to a BG thread or anything, they are purely for supporting JS targets.

If you do not have js/web targets, set generateAsync to false and simply call the non-suspending function from your suspend functions in the appropriated thread context (e.g. Dispatchers.IO.limitedParallelism(1))

Again, contributions via PRs are always welcomed!