Kevin

We never came back to it. There's still a draft PR open but i no longer think we should implement our own priority-aware mutex, we could leverage `async-mutex`'s semaphores which...

Hi @barbalex, the issue with `upsert` may be the same as the one you encounter previously (https://github.com/electric-sql/electric/issues/782). It looks like the boolean value which internally is stored as an integer...

Hi @barbalex, i've not yet found the time to look into this bug. I hope to find some time soon to investigate further.

Hi @barbalex and @KyleAMathews, i tried reproducing this issue using your examples but didn't manage to reproduce it. I used your exact schemas and in case of Kyle the same...

Hi @ygarg465, what exactly is the problem you're facing with `makeBooleanFilter`? Looking at the code you do have an implementation for `makeBooleanFilter`. Is that code working? Or is that code...

@ygarg465 Do you understand the changes that are needed to make it work with `or`? I'm fine with changing to a better approach to build these queries (using Kysely). I...

Parsing the service URL with `new URL(...)` is a great improvement! Not sure about throwing an error versus logging a warning. @thruflo and @samwillis may have an opinion on this.

Hi Chris, ignore what i said above. I was experimenting with different models and I must have seen some old state (probably forgot to re-generate). Prisma does not seem to...

Sorry for the confusion, the problem i describe above does occur, but not for `itemsFindUniqueArgs` (that was my IDE being confused). The problem occurs on `Prisma.itemsAggregateArgs` and `Prisma.itemsGroupByArgs`. See here...

@fotoflo I have experienced similar issues indeed. So there are 2 problems: - Prisma does not seem to be consistent in their naming. For most types they keep the capitalization...