Hello everybody, Is there a method to soft delete? Thanks

Do we have documentation on a connectOrCreate equivalent in mutations? Something like rails’ findOrCreate? It’s not obvious where this ended: https://github.com/graphcool/prisma/issues/1280#issuecomment-352201407

I am still unable to

deploy

and graphcool framework config to any graphcool clusters. I have been deploying the same project for months, to numerous clusters/instances and updating existing ones over hundred times… ever since the issues last week

deploy

gets a cloud front timeout error…. nilan suggests I can separate the schema into multiple files with less type defs and

deploy

it several times in chunks… anyone know how to do this?

ICYMI: https://github.com/graphcool/prisma/issues/1734 was fixed in

1.5.2

🎉 🙂

Will the ability to manage connection pools be available in the PostgreSQL Connector for Prisma?

There used to be a Prisma roadmap on github. Is there still one around?

Is there a guide or is it really simple to switch from a local cluster to a dev cluster?

hey!

Does anyone if one can mix forwardTo with custom resolvers. The context is wrapping a rest API, for the most part i want to maintain

forwardTo(db)

but want to nest some data via a rest API.

don't think its possible but want to avoid another resolver for what i really want to represent as nested data to my existing datamodel

just wondering if anyone knew

has anyone tried using graphql-yoga with AWS Lambda?

@kaiba yes im using it now with aws lambda

Did you use 'handler.playground' as the Handler for the Function code config on your lambda function?

@harrisrobin ^

hey guys, new to graphcool… How would one go about importing an existing MySql DB w/ prisma service

I’m just getting up an running with the lovely -> https://github.com/graphql-boilerplates/node-graphql-server/tree/master/advanced

ahh

As of today, the conversion from any concrete data source (like MySQL, MongoDB or Firebase) to NDF must be performed manually.

whats the difference in prisma cloud between running on their clusters and running on your own cluster/mysql database?

does any one have a link to the docs for the legacy console?

does anyone know if it's possible to install/import node modules for serverless functions inside the legacy console?

in that serverless legacy console function, i'm needing to send a post request to a remote api, but the

fetch

and/or

https

includes do not seem to be supported, even though they are natively part of the node api for example, the following does not work:

const fetch = require('fetch')

const https = require("https")

const fetch = require('isomorphic-fetch')

Hey everyone, I was just wondering, if there are any complete guides on how to deploy a full prisma application to a root server running Ubuntu. I would like to host my first project like this to save some money until it scales up, concerning user counts. (including graphql-yoga server)

anyone able to help me understand what SharedLink does in the prisma-binding ? https://github.com/graphcool/prisma-binding/blob/master/src/SharedLink.ts

Hi, this is my first time trying to deploy React/GraphQL/Prisma app. I deployed my Prisma cluster to AWS Faragate following this tutorial (https://blog.graph.cool/how-to-deploy-a-prisma-cluster-to-aws-fargate-using-docker-cloudformation-293aa8727b89). Now I'm trying to figure out the next step. What would be the best way to deploy the rest of the React+Prisma app on AWS (i.e. EC2, S3)?

Can some of you guys describe your versioning strategy and deployment workflow for your GraphQL server + Prisma stack?

Can anyone using Prisma recommend how to handle

resolveType

issues? After updating Prisma and graphql-tools, we started getting the following warning:

Type "Node" is missing a "resolveType" resolver. Pass false into "resolverValidationOptions.requireResolversForResolveType" to disable this warning.

there seems to be an issue when using setHtml with a long html string when using chromeless({remote:true}) , locally works fine though can have as long html-string as you like

Anyone else encountering this issue?: https://github.com/apollographql/graphql-tag/issues/77

I'm attempting to migrate a working, prisma-backed, node EC2-based, graphql server to AWS Lambda. The function seems to be working up until the point at which the server makes a call to prisma. Then, in the server/lambda log, I get back: [Network error]: TypeError: Only absolute URLs are supported. Any thoughts?