Hi 🙂 When will this feature release? Waiting Impatiently.

Realtime and Native GraphQL Syntax.

Not yet supported as golang.

Hi @ all, i have a minimal question to the folk. It's possible to forward prisma generated filters for queries from GraphQL?

I was wondering if someone can point me in the right direction when w/ working with arrays/lists. I can't seem to figure out what I am not doing correctly (it is worth noting that if i take prisma out of my work flow I can get the expected results of pushing items from my front end as an array of items in my database.) I will post a couple screenshots of what I have under this thread.

I've got a prisma server running on my local machine and I am trying to build another prisma server on the same machine. Predictably the container for the DB complains 'ERROR: database "prisma" already exists.' what's the sane way to resolve this conflict?

change the DB name on the docker-file.yml

database: DB_NAME

Thanks

is there any Long Int type for prisma datamodel

or what's the best way to store phone numbers except for string !

Has anyone else come across the issue with TypeScript (any versions later than 3.4.5) where you see the following? Expression produces a union type that is too complex to represent

GitHub issue here: https://github.com/prisma/nexus-prisma/issues/291

I’m seeing it in my resolvers.

It basically means everything in my resolvers has the red underline warning. The only workaround is to pin to TS 3.4.5. Any idea how to actually fix this?

I’ve got a situation where I need to use something akin to union on my input types, but it is not part of the spec yet. See https://github.com/graphql/graphql-spec/issues/488 if you want to dive deeper into why I might need something like this. But I was wondering if anyone else has come across a scenario where you want one and only one of the input fields to be non-null? If yes, how did you solve it? Currently I am simply doing this:

input MySuperInputType {
  a: MyFirstInputType
  b: MySecondInputType
}

input MyFirstInputType { date: Date! }
input MySecondInputType { someText: String! }

And after that I am relying on the server implementation to do the validation that only one of them is null. But this seems like a really bad way and it doesn’t let the client know that only one of these fields can be supplied. Does anyone have a better way?

docker ps

Hi, does anybody have time for a basic question with nexus prisma. I've been trying google foo but maybe it would help to have someone explain this to me. My problem is when implementing a custom resolver, none of the non scalar fields return with the type I have defined (in this case I'm expecting a list of Users) and so when grabbing it, it's obviously null. I've been sorting through resources but may have overlooked something. Anyone available to point me in the correct direction?

Hey, I am a huge fan of Prisma and used it for multiple projects. All this time I was using Node but I am learning Go and I really like Go. I am able to run gqlgen by 99design without any problem but when I load the Prisma models it starts to get a little wonky. I followed the docs on Prisma's website but can't get a hold of it.And the docs seems a bit weird.

Like for a mutation resolver for creating a new User they are only taking name as a input when in the Schema a User has name as well as email. Hmmm???? I think it gqlgen not being able to parse the Prisma models properly. Any help would be awesome.

Hi everybody, I'm fairly new to Prisma and can't seem to understand how it works in the "big picture". My traditional setup was api endpoint using knex.js which talks to the database. Now when using Prisma I'm a bit confused, it is working on my local machine using docker-compose but to be honest have no idea on how it would work to go to a live environment. Specifically how do you make sure that the live database is in tact with the changes you made locally without losing data etc.

Would love an example on how a deployment would work and how 1. The model of a Postgres database will be changed to match the local one (normally using raw SQL scripts or an orm to provide the up and down migration) 2. How will Prisma in deployment know / understand the changes?

is prisma2 init working for somebody ?!

I just get

Error in lift engine

there's anyway to get output log to understand what is going on?

I am using prisma2@2.0.0-preview1

Is there a general way to handle the case where you have an edit form that submits to the API and if the person tabs past the input it sets it as an empty string. Then when it gets submitted to the server it blows up b/c the empty string wasn’t expected? Thats annoying. How do you typically handle this other than brute-force delete them off the object on the client-side.

I have a form I'm using in React where there is a field I have for a date but it isn't required. Right now I have it set to an empty string to start and if the user fills it out then it's replaced by the date. If the user doesn't change the field I get an error though for sending an empty string when the server is expecting a date. What value should I use as default to avoid that error?

Why is there no way to call async functions in enumType in Nexus? What if we want to dynamically populate the enum from a table? I can't be the only person to ever think of this.