It's a blocking call the same as is deserializing from a string

Not sure halt is the correct terminology. If it is sourced from a file - It will it block while the whole file is read. Is that right?

Yep!

I’m having trouble getting schema module dependencies in sqldelight to work after updating to kotlin 1.6.20 or later. I have a few queries that join on tables in the shared module, and all of those are now failing to compile with the error

No table found with name <shared table name>

. Switching back to 1.6.10 immediately fixes the issue. Any ideas what the problem could be?

Hi everyone, I’m using sqllite for my KMM project. My query is something like this:

CREATE VIEW IF NOT EXISTS FinalView AS
SELECT
    a.id,
    a.id1,
    a.id2,
    b.id,
    b.id1,
    b.state,
    c.id,
    c.id1,
    c.version,
    d.id
FROM
    A a
    LEFT JOIN B b
        ON b.id =  a.bId
    INNER JOIN C c ON c.id = b.cId
        AND c.version = a.version
    LEFT JOIN (SELECT * FROM D d
                      WHERE d.state = 'COMPLETED'
                      AND d.id = b.dId
                      AND d.id2 = a.id2
                      ORDER BY d.sessionNo DESC LIMIT 1) AS dLast ON d.id2= a.id2
        AND d.version = a.version
;

In this I’m facing an issue where AndroidStudio is saying that it is not able to find table b and d in my subquery statement. Can someone please let me know what I’m doing wrong here?

I’d been skimming through Molecule’s code and wondered if the Recomposer should use

this

as parameter (as in,

this + clockContext

), otherwise it still uses the original

coroutineContext

https://github.com/cashapp/molecule/blob/dcfea3afe82d834643345c44b45522eee5b6c64a/[…]ule-runtime/src/commonMain/kotlin/app/cash/molecule/molecule.kt

is there a way to use

Paparazzi

just for Android app module in a Kotlin Multiplatform project?

Getting compiling error when using molecule in macos, more in thread

Looks like you’re using it as a static method?

buffer

is an extension function so you’ll need to do:

sink.buffer()

[SQLDelight] Is it possible to create a column adapter on a QUERY column, not on a TABLE column?

no, recommendation is to just do the conversion on the kotlin side

you can do SQLite `CAST`s if thats helpful

to cast to a different data affinity

But not to List, right?

correct

From, say, group_concat?

Is this something you'd like to be supported in the lib? If so I can work on it and maybe make a PR?

no, its not

its come up a few times in the past

but my brain has offloaded the exact reasoning why

its probably under the category of things that introduce a ton of complexity and would rather just keep the complexity in kotlin instead of sql

Don't want to appear dismissive or rude, I'm just wondering why this is considered good on the table creation side of things and not queries? Seems like something that would help to omit quite a lot of boilerplate

Oh ok, complexity management is a reasonable philosophy 🙂

yea you're not its all good

in general I'm more okay tweaking the DDL than I am the DML

since create tables are pretty simple

and you are already specifying type information there

where in a query its doing more inference

this isn't always true, but its true enough of the time that its a clean separation