any help I could get is appreciated

using SQLDelight 2.0.0 with kotlin 1.8.22 and coroutines 1.7.3

Perhaps https://github.com/cashapp/sqldelight/issues/4376?

I feel like this is a noob question, but maybe I'm missing something basic? My mind kinda goes towards rxdogtag so maybe something like that just exists for coroutines (all of the network calls seem to be suspend functions) So I joined a new project recently and am a lone dev trying to pick up the pieces. our most popular crash on crashlytics is

Non-fatal Exception: java.io.IOException: canceled due to retrofit2. HttpException: HTTP 503
at okhttp3. internal.connection. RealCall$AsyncCall. run (RealCall. kt : 530)
at java. util. concurrent. ThreadPoolExecutor. runWorker (ThreadPoolExecutor. java: 1145)
at java. util. concurrent. ThreadPoolExecutor$Worker. run (ThreadPoolExecutor. java: 644)
at java. lang. Thread. run (Thread. java: 1012)

but im confused on how to take anything actionable from that. There's literally no other information. Is there someway to update the app so that I can get a stacktrace to a callsite in the app code?

Hi, does OkHttp handle defragmented Websocket Frames automatically? as per the spec the client/server can set the

FIN

flag to indicate if this is the final fragment in a message. The

onMessage

callback in WebSocketListener doesn’t mention if the returned payload is the defragmented message or no?

Alright... riddle me this. I'm using SQLDelight and I suppose I'm missing something fundamental here. Querying my db (to see if a value exists) while I have a large transaction ongoing prevents the query. Am I doing something blatantly wrong here? Code in thread

I wonder since AndroidX Paging now is a mutiplatform project with macOS support, I wonder can we get macOS support in sqldelight-androidx-paging3?

Hello, is there a tutorial to use SQLDelight on a multiplatform project that includes web?

Hey there, a question about SQLDelight: I'm using the in-memory JdbcSqliteDriver in a jvmTest and I'm greeted with a

SQLiteException: [SQLITE_ERROR] SQL error or missing database (cannot start a transaction within a transaction)

. This probably happens because the tested object ends up creating two non-related coroutines which both call

db.transaction { ... }

. And particularly in the test environment there's a good chance they run at exactly the same time. So if someone could help me out with these questions it'd be great: • Does this only happen with the InMemory JdbcSqliteDriver driver, or potentially also with the regular JdbcSqliteDriver and Android drivers? • What are my options to handle this scenario? The easiest I can think of is a single-threaded Dispatcher that I use for all database transactions.

In SQLDelight, can you configure via sqldelight gradle plugin if I want to change the way data class table are generated? Example: (Person -> PersonTable or PersonDbEntity)

I have defined a table as

NOT NULL

in the past and now I’m altering it within a migration with:

ALTER TABLE X
    ALTER COLUMN Y DROP NOT NULL;

I have

deriveSchemaFromMigrations.set(true)

in my gradle file. Still, the generated data class and inserts are not marking those fields as nullable. I have tried to run

generateDatabaseInterface

with no luck. This is PostgreSQL, btw. Any idea why this could be happening? 🙇

Hey! I was wondering if somebody could either explain or link me to an article explaining how to sync my database models across multiple projects in SQLDelight. For example I have 3 projects, [app1, app2, api]

api

will hold all my SQLDelight queries and models and I want app1 and app2 to stay in sync with that. I was trying to find an article or something explaining how to properly do this but just haven't really found much, and I'm not sure if the official docs say how to do this either.

[SQLDelight - question about grouped statement] Is there a way to specify object parameters in grouped statement?

@ralf Can we find suffix for these compat releases that does not make renovate think the compat release is more up to date than the real regular release?

I've switched to use the generate async option in sqldelight and on iOS every now and then I'm also running into - https://github.com/cashapp/sqldelight/issues/4376 Are there any plans to cut a 2.0.1 or 2.1.0 anytime soon?

Hey I'm trying to add Okio to my js-node KMP project as described here https://square.github.io/okio/multiplatform/, but Android studio can't resolve node filesystem

Failed to resolve: com.squareup.okio:okio-nodefilesystem:3.6.0

I have no problem with the core

com.squareup.okio:okio:3.6.0

Post 1.2.0 getting a stackOverFlow in Zipline Any idea why below might be happening. this is v1.6.0

Does Anvil have issues with kotlin 1.9.20 ? I am running into weird stuff and always need to run with --rerun-tasks to make sure it compiles correctly.

What is the latest snapshot version of SQLDelight? I'm specifically looking for a version that solves this issue on multiplatform https://github.com/cashapp/sqldelight/issues/4598

[SQLDelight - Errors when selecting from VIEW] Whenever I run gradle generateMainWhiteCloakKpiDatabaseInterface, I encounter issue:

Unexpected column alias parent {}: []

Hi team, I’ve got a testing question. It only very loosely relates to Turbine, I’m sure it’s a more general coroutines/testing problem. But I thought I’d ask here anyway. It’s to do with testing the interactions between a Channel and a SharedFlow. See 🧵

Our team has a strict policy on fixing all Strict mode violations. Last comment was two years ago... anyone know off the cuff if anything has changed, or can should I just say that it's infeasible to fix for now? https://github.com/square/okhttp/issues/3537

Hi, I have an issue that I am stuck on when trying to convert my SQLDelight R2DBC setup to use connection pools. Not directly an issue with SQLDelight, but rather R2DBC but it is really strange so I am asking for help here. When using R2DBC it seems like the driver detection only finds either the "pool" or "postgresql" driver but not both. I already specify an "api()" dependency on both the postgresql and pool modules in the gradle file. Whether the "pool" or "postgresql" driver is loaded in a particular build is apparently random and I suspect it's based on the order in which I define it in

build.gradle.kts

. But always exactly one of the two drivers gets detected. Here is the erroring code (just trying to make a R2DBC connection pool):

pooledConnectionFactory = ConnectionFactories.get(
    ConnectionFactoryOptions.builder()
        .option(ConnectionFactoryOptions.DRIVER, "pool")
        .option(ConnectionFactoryOptions.PROTOCOL, "postgresql")
        .option(ConnectionFactoryOptions.HOST, config.host)
        .option(ConnectionFactoryOptions.PORT, config.port)
        .option(ConnectionFactoryOptions.USER, config.username)
        .option(ConnectionFactoryOptions.PASSWORD, config.password)
        .option(ConnectionFactoryOptions.DATABASE, config.database)
        .build()
)

This is the error (in this case it found "pool" but didn't find "postgresql"):

Exception in thread "DefaultDispatcher-worker-2" java.lang.IllegalArgumentException: Could not find delegating driver [postgresql]

I have a really unusual setup though. The project is a multi-module KMP project, and the module I am building compiles to a Minecraft plugin (Spigot API) which loads after the game server itself, so that might be a potential issue. The module that has the R2DBC dependencies is different from the Minecraft module which is being compiled. Both of the dependencies do show in the compiled JAR file as shown in the image below. Anyone know what is wrong with my setup and how to get both drivers to be detected?

At least one of my PostgreSQL R2DBC update functions in SQLDelight gets stuck quite often. It never returns and also does not cause any effect in the database. I've tried pretty much everything that I can think of at this point, and this still happens. • The PostgreSQL database is running on the same computer as the server application • When I list running queries in PostgreSQL, nothing shows up, so the query isn't just stuck in Postgres (it's also just a simple UPDATE query) • I added print statements right before and after the calls to SQLDelight. Only the message printed before the statement gets shown and the one after the statement doesn't. • I tried running the calls in different coroutine scopes (for example launching it as a fire-and-forget operation in the global scope), it still gets stuck • I thought the issue might be my custom connection pool implementation, so I switched to r2dbc-pool and finally got it working today. However, the exact same issue still happens • I noticed that it seems to get worse / happen earlier with a lower connection pool size Is this a SQLDelight issue or an issue with my configuration? Honestly feels like I should stop trying to use r2dbc and switch to JDBC with

withContext(<http://Dispatchers.IO|Dispatchers.IO>)

instead because of how little support/testing seems to have been done (another example is how the BYTEA data type still doesn't work after I reported it a few months ago).

This message was deleted.

SQLDelight

2.0.1

👀

dont get too excited every time i go to release some publication issue comes up that takes me all day to fix

okay it worked

SQLDelight 2.0.1 is out 🎉

will take some time to propagate through maven