Dominic Petrick

@aladinflux Your datamodel didn't actually work for me, I needed to change the key references to `User` (e.g. `author_id`) to `String`, from `Int` (that's a bug in the validator). Then...

You can't use Prisma without a replica set, my local setup is also a one-node container. I'm not saying that this issue doesn't exist, because the OP illustrates this is...

@chrisschaub Do you have a somewhat reliable reproduction, or maybe some load parameters to make it likely to run into this problem?

@chrisschaub Is it possible for you to extract a small reproduction that, if run locally for you, fails with the write conflict?

Thanks! 4.4 is perfectly fine,, no need to upgrade.

Thank you for the info, that's helpful.

Can you be a bit more specific? You mean the readme?

Discussed with @pimeys that we should probably just rename `NoCondition` to something more expressive, like `TrueCondition` and `FalseCondition` to avoid setting the wrong expectations.

Note that this may increase perceived performance for a group of queries but reduce overall perceived query performance of the system in high-volume loads. - All queries of a batch...

Thanks, will take a look.