Stephen Haberman

Mikro's version of multi-level loading: ```ts await authorRepository.find( {}, { limit: size, populate: ["books", "books.reviews", "books.tags"], orderBy: { id: "ASC" }, }, ); ``` ```sql select "a0".*, "b1"."id" as "b1__id",...

Another example of "multiple left joins" tripping engineers up: https://gist.github.com/rxliuli/be31cbded41ef7eac6ae0da9070c8ef8#avoiding-multi-table-left-joins

This will be another tough production test case: ```ts export const costCodes: Pick = { costCodes(root, { filter }, { em }) { const { tradePartnerIds, version = [1], ...others...

Prisma: ```ts await prisma.author.findMany({ where: { OR: [ { books: { some: { title: "b2", reviews: { some: { rating: 2 } } } } }, { books: { some:...

Hi @sacesare , thanks for filling the issue! What are your primary key columns typically called? Are they consistent across your schema, or do they vary table-by-table? Joist's unit-of-work approach...

> information_schema I don't use `information_schema` on purpose, b/c postgresql implements `information_schema` as (expensive) views on top of its raw internal `pg` metadata tables, and the performance of using `information_schema`...

Hi @Jille ! Just looking at what we do now, we do use the shebang in our `protoc-gen-ts_proto`: ``` #!/usr/bin/env node require('./build/src/plugin') ``` But, right, the rest of the ts-proto...

Hi @frenzzy ; this makes sense. Fwiw it should be an easy fix by just adding a "t:" prefix to the import symbols for ts-poet, which is the underlying code...

Hi @cgcoss -- sorry, I didn't see this comment until after already merging your PR 😅 , so didn't realize you'd meant it as still WIP. Happy to have more...

@chr1sjf0x cc @zgavin thinking about the "testing a resolver in dry-run mode" use case, I think that makes sense, but wonder if we could support it w/o having `mapToOriginalEm` end...