Hi there.
I am using drizzle graphql for my application. My drizzle schema is getting pretty complex as the app grows, but nothing out of the ordinary.
When I am generating the graphql schema using drizzle, the ram consumption sky rockets, and crashes the app because it eats up all the allocated ram (I have allocated 12 GB!).
I geuss this is because of all the nested relations that is generated for each model in the database.
Maybe there is an obvious quick fix for this? Otherwise it would be nice with a solution. What about a setting for buildSchema, where you can declare how deeply nested the relations in the generated schema should go?
Hi there.
I am using drizzle graphql for my application. My drizzle schema is getting pretty complex as the app grows, but nothing out of the ordinary.
When I am generating the graphql schema using drizzle, the ram consumption sky rockets, and crashes the app because it eats up all the allocated ram (I have allocated 12 GB!).
I geuss this is because of all the nested relations that is generated for each model in the database.
Maybe there is an obvious quick fix for this? Otherwise it would be nice with a solution. What about a setting for buildSchema, where you can declare how deeply nested the relations in the generated schema should go?