Tristan Siegel
Tristan Siegel
@janpio the temp solution does not work for me on trying to up the connection limit ``` const prisma = new PrismaClient({ datasources: { db: { url: `${process.env.DB_URL}?connection_limit=10` } },...
I ended up going with a modified solution based on @mkalam-alami's approach. The issue is that the `tsconfig.json` at the top level sets a `baseUrl` that makes sense for the...
Interesting, maybe it's the language in the docs, but I assumed that the following meant that if you say a field is dependent it will always be provided in the...
@danielrearden I was able to scope it down to an issue with my tsconfig. Having `"esModuleInterop": true,` causes the issue, which is surprising since your target output for `sqlMancer` is...
Hey @danielrearden this has gotten me unblocked! I figured I'd share my schema here for others so they can see what I did. It looks like I need to make...
Seconding this!
I'm not sure how helpful this is, but I figured I'd share why I started using SqlMancer, what I'm using it for, and what I do and don't like about...
I think @wtrocki makes a lot of good points, specifically about the problem of allowing a graphql schema dictate your database schema. I'm currently running into that issue now, and...
Sounds like a new kind of schema :) but whatever you call it, I think that's probably the right approach