How are you guys passing env variables? Do you need to do

prisma deploy --env-file .env

everytime?

@mxming @tomhut Can you please check whether the API is back again? Just need confirmations

it is back for Asia Pacific region for now

thanks for the help to get it up

@Harshit Looks good to me, I can't see any more errors on our front-end analytics and my tests are passing from our asia-pacific region 😄 Thank's for all of your work getting this back online!

is there a channel for questions about nexus and graphql-yoga?

i don’t get it why in the javascript example of photon nexus is not used, and it is used in the typescript example https://github.com/prisma/photonjs/blob/master/examples/javascript/graphql-auth/src/index.js

what’s the best way to do a pagination in nexus-primsa with prisma v1 if Relay compatible pagination does not work?

👋 hello, I'm suddenly having trouble connecting to prisma server using the generated javascript client. It has always worked with the env var

PRISMA_MANAGEMENT_API_SECRET

injected into the docker container correctly and suddenly after a deploy and a generate I'm getting this error

"Your token is invalid. It might have expired or you might be using a token from a different project."

Any ideas?

What happened to the vscode extension for Prisma v1?

Since the Prisma team isnt that focussed on GraphCool anymore, which I still believe is an awesome product, can they at least provide an EASIER migration path to Prisma? Its a little complicated now. Can they take care of migrating to Heroku or something by default? I am sure existing Graphcool customers are willing to take it from there.

another downtime for graphcool in Asia Pacific region ??

2 questions here for those of you who may be more experienced with this framework than me 1) I'm a bit confused why a field named

createdAt

is being recreated when it already exists. I read the various issues and understand that both

updatedAt

and

createdAt

are reserved in prisma, but using it would simply expose already-existing columns. The error I get is

org.postgresql.util.PSQLException: ERROR: column "created_at" of relation "addresses" already exists

, and the only way to get around this seems to be to remove the field from datamodels altogether.

2) I already have

migrations: false

in my local docker-compose file, yet the DB is seemingly trying to make and apply migrations. This seems troubling tbh.

Hey Prima peeps. I'm having a bit of an issue setting a unique field to

null

in a mutation and unsure if it's a bug or if I'm approaching this wrong. Would anyone be able to offer some advice? Rough overview of the problem is: - Create an object with a

@unique

field explicitly set to null - Create another object with the same field explicitly set to null

...
"message": "A unique constraint would be violated on User. Details: Field name = email"
...

Hey all, I have a bit of a doubt. I have a

login

resolver which I call from ApolloClient, but I decided to add a Login with Twitter button and the logic lives in ExpressJS. Here's my callback:

server.express.get(
  "/auth/twitter/callback",
  passport.authenticate("twitter", {
    failureRedirect: "/twitter_failed",
    session: false
  }),
  (req, res, next) => { 
    
    // <-- invoke `login` mutation 

    res.redirect("<http://localhost:3000/>");
  }
);

My doubt is how would you call a mutation from

express.get

?

hey i have just realized i cannot used prisma2 as it is not mature yet, and i would like to use prisma 1, it seems the default prisma cli is 1.32.2 but on the website i see 1.34 is the latest

then when i update i get this

it goes back

i reverted to prisma1 and now i’m trying to write my datamodel.prisma but the vscode plugin thinks its prisma2

i tried to uninstall the prisma extension which clearly states its for prisma2 but then the other graphql extension does not know how to deal with the .prisma file

Hey anyone 🙂 has anyone found a workaround for this? *[Mongo] Cascading deletes * https://github.com/prisma/prisma/issues/3796

no one 😞

@JBriggs That's a huge limitation of MongoDB connector in Prisma v1. Maybe it'll be fixed in Prisma2 (?) https://github.com/prisma/prisma2/issues/267 cc @nikolasburk

@Ivor thank you for that, alas, I was not really interested in using prisma 2 😕

perhaps they could implement on v1.34 ++

😛

Hi, I'm setting up a daily cron for my db backups via mysqldump

Should I copy all the databases including prisma, default@default, information_schema, performance_schema and sys?

Just wanted to ask here how people's experiences have been of Lift migrations? I've found that after introspecting an existing highly relational db schema and pushing it to a new db, I essentially can't do any migrations as so many tables are being altered which violates foreign key constraints. There's a github issue here: https://github.com/prisma/lift/issues/100. Seems like quite a big thing and wanted to hear how others have found it?