I usually add my test queries to the main

.sq

file and prefix them with

test

You could create another module

test-queries

, add the main database as dependency and depend on the test module in

commonTest

.

Hey, is there any thought on when a new retrofit release might be planned? Would love to have access to https://github.com/square/retrofit/pull/3702

Probably a month or two still. I'm on paternity leave.

hello, i'm using the cashapp multiplatform-paging library, works great for android but i'm unable to access the uikit runtime from xcode. i've added the api dependency to iosMain but can only access the types from the common library. is anyone using this library on ios that can help me? i was unable to build the sample project and found no other examples online

is it thread-safe to request multiple transactions from different threads on JVM with sqlite? Using the provided

JdbcSqliteDriver

val database: Database = ...
val queries: MyQueries = database.myQueries

// request for transaction in thread A
queries.insertPerson("Joseph")

// request for transaction in thread B
queries.insertPerson("Martina")

I'm using SQLDelight. Is there a way to validate that existing database table structures matches latest code definitions? Right now if I don't have appropriate migration, app crashes with stacktrace that uses no project files - probably because I'm using flows, so it's hard to catch DB exceptions and recreate DB.

if I understand it correctly, this can help me on build time to verify migrations, e.g. in CI task. but how can I use it in runtime to clear existing database when it has been changed?

You have to do that yourself

Use empty migrations to increase the database version and then an upgrade callback to delete all tables and run schema creation

How can I test such a case?

@Test
fun shouldTimeOut() = runTest {
    suspend fun number(): Int {
        delay(2000)
        return 1
    }

    flow {
        emit(0)
        withTimeout(1000) {
            emit(number())
        }
    }.test {
        assertEquals(0, awaitItem())
        assertTrue(awaitError() is TimeoutCancellationException)
    }
}

I get

No value produced in 1s

rather than a timeout exception

If you increase the time until the turbine fails, what do you get?

Increase the timeout of Turbine by passing 3.seconds as first argument to test function

Although our timeout is a wall clock one and your test should be entirely on virtual clock

By setting the turbine’s timeout to 3s, I get

No value produced in 3s

hmm you're using

runTest

which skips delays so your

delay(2000)

and

withTimeout(1000)

should return immediately

Are you on the latest version?

If not, try. If yes, file a bug and we'll look.

I’m using 0.12.1 I did some more experimenting and found that this works :

I think I know what's happening.

ReceiveChannel<T>.awaitEvent()

is receiving the

TimeoutCancellationException

and it's incorrectly thinking the test actually timed out

Hmm. So we need to use a custom exception type internally.

Easy fix. File a bug, please!

isn't

TurbineTimeoutCancellationException

already our custom timeout exception?

Will do right away, thanks for the quick help!

I have a question about SQLDelight and how it returns a new Flow value when the database is updated. How is the update logic implemented?

Any queries that write to any tables used by a query will get a callback to rerun. It's a really basic system, and it means you have to issue writes using SQLDelight