Hello, I'm trying to start Prisma with my existing Postgres DB where I have a table named "member" and this table has a column with the name "birth_date" that is just a date value with no constraint to other tables. I'm getting the following error when I try to deploy Prisma:

!    The Migration failed and has not been performed. This is very likely not a transient issue.
!    org.postgresql.util.PSQLException: ERROR: column "birth_date" of relation "members" already exists

Anyone has any clue why I'm getting this error?

Hi, is there a way to connect Prisma to Cloudera Hadoop??

New account signed up. The Prisma console seems buggy

Try adding a server to my account through Heroku "(HTTP code 404) unexpected - manifest for prismagraphql/prisma:1.34.9-gatsby-heroku not found"

Anyone know what to expect if an

Enum

field type is changed to

String

with data already in the DB? Fingers crossed it leaves the values in place and converts them to string type?

✨Hey folks! ✨ Prisma is hiring and so are a bunch of other cool companies. We’ve written up the details in the #job-listings channel, and you can see all of the other community opportunities there as well! 🙌

hi! when I start my prisma project I'm starting to get this:

/Users/morten/Code/test-project/node_modules/nexus-prisma/dist/definitions/objectType.js:30
    return nexus_1.core.nexusWrappedType(typeConfig.name, function (builder) {
                        ^

TypeError: nexus_1.core.nexusWrappedType is not a function
    at prismaObjectType (/Users/morten/Code/test-project/node_modules/nexus-prisma/dist/definitions/objectType.js:30:25)
    at Object.<anonymous> (/Users/morten/Code/test-project/lib/schema/query.js:4:18)
    at Module._compile (internal/modules/cjs/loader.js:945:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:962:10)
    at Module.load (internal/modules/cjs/loader.js:798:32)
    at Function.Module._load (internal/modules/cjs/loader.js:711:12)
    at Module.require (internal/modules/cjs/loader.js:838:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/Users/morten/Code/test-project/lib/schema/index.js:8:9)
    at Module._compile (internal/modules/cjs/loader.js:945:30)

using Prisma 1 together with

"nexus": "^0.12.0-beta.6",
    "nexus-prisma": "^0.3.8"

this started happening after I deleted package-lock.json and reinstalled npm modules. anyone seen this? tried googling it without any luck. if I downgrade

nexus

to

v0.11.7

it works. maybe that's the best approach then

Hi prisma team! I can’t create a server on prisma cloud, there seems to be an error

Anyone available for PrismaCloud Support?

Hey all, I'm looking for some advice on production profile (not necessarily specific to Prisma, I guess). I've deployed a container on AWS fargate and a graphql server using Apex Up. I have some pretty simple mutations that take around 600ms - 1.5s to run, which is a bit unacceptable for the use case. When I run it locally, it runs almost instantly. All my AWS stuff is colocated in us-west. I'm not super familiar with AWS, was wondering if anyone has advice on how I could investigate the slowness and profile requests? Because other GraphQL queries run fast, I assume it's due to somewhere between the graphql-yoga server and the Prisma Fargate container.

I have upgraded the mongo version from 3.6 to 4.2.1 so do it break any thing in prisma 1.36

I have a demo server on prisma cloud that I need to deploy to PRD. I didn’t find any plan of prisma cloud for prod so i want to deploy to AWS. How do I export the data from the MySQL demo to my own mysql? Can I connect to the demo MySQL server manually?

ok I found prisma export

Hey. I created a prisms service with postgress the n used same docker instance to create another service on the same database but there seems to be a conflict; since both schemas for both services had the User type I can query users from the second service and get users from the first service. It seems the postgress db merged the schemas or something . And now when I switch back to first service I can't query users it sends this message

Did anybody used knex or any other similar tool along side prisma? I’m trying to implement some basic queries and mutations that prisma does not support

With Nexus how do I pass through a sub GraphQL that's not Prisma?

I ran through a small misunderstanding while being in the schema.graphql file. I have noticed that graphQL has a different way of understanding query: String and query : String Note that the first one does not contain space between the key and column. I just wanted to understand what causes that. Is it an issue related to GraphQL ?

hi! can any one help me with example how to seed enum? details is there https://spectrum.chat/prisma/graphql/how-seed-data-with-enum~9deb82df-30a5-486a-b5ff-2242704d59e2

hey guys, one question... we can connect our front end using Apollo as explained in this tutorial https://www.prisma.io/docs/1.10/tutorials/connect-to-prisma-from-the-frontend-fbgaeyrou7 but it's also mentioned that the implementation is not good for a production setup, but for prototyping. What would be the right architecture for a production environment then? Thanks! 🤙

@christian You need to add prisma to your server setup, where you can use it with Apollo Server making your graphql server. Then, on your front-end client app, you make querries and mutations to acces the server

Hello! 👋🏽 I’m having an issue with implementing relations with Prisma client, but only on our live app, not on develop. I reviewed the Guide to Common Resolver Patterns (https://www.prisma.io/tutorials/a-guide-to-common-resolver-patterns-ct08#scenario-implementing-relations-with-prisma-client) and confirmed that everything is implemented as described there. When I make a request for an object with related child objects, I get back an empty array on the live app only. Develop seems to work as expected. Has anyone encountered this issue before? Any info would be helpful! Example of query:

Query:
{
   object(where: { id: "someIdStringHere" }) {
       UUID
       childObjects {
            Attribute
       }
   }
}

Example of call with Prisma client:

In the API: 
   context.prisma.object({ id: "someIdStringHere" }).childObjects();

Result: []

Hello Guys, someone knows how to declare in a prisma2 model a property as a JSON Object ?

Team, do you know how to set timeout while creating graphQL client? I’ve found GIT issue https://github.com/prisma-labs/graphql-request/issues/103 which suggests to use timeout Option. This is not working as is. Can you please help me with this?

Hey, Can anyone guide me on how to add a custom directive in Prisma 1 using

nexus and nexus-Prisma and graphql-yoga

. I am struggling with this and haven't found any solution. Started with this article https://medium.com/@lastmjs/advanced-graphql-directive-permissions-with-prisma-fdee6f846044 but this doesn't seem to be working now.

Hey, Can someone please give me some directive on a grapqhQL approach. I have seen so many ways of implementing graphQL namely with express-graphql , with graphql-yoga and so on... what for you is the method worthy to learn ?

Any Idea if prisma is going to support c#/asp.net ?

Hi, It was been a long time since I was watching Prisma, quick question: Can I use prisma without deploying a docker image?

my only concern is the name, back in may, palo alto rolled out a service they are also calling prisma. https://www.paloaltonetworks.com/company/press/2019/palo-alto-networks-introduces-prisma--the-secure-way-to-cloud

if it werent for that i would be using it

Is it possible to make all of these queries to the prisma DB in a single call versus doing this. Essentially I’d like to retrieve the fully populated

context.prisma.droneBuild({id: buildId})

with all of it’s downstream parts in a single network request, rather than having to make 10 queries to retrieve that information.

const flightController = await context.prisma.droneBuild({id: buildId}).flightController().flightController()
  const esc = await context.prisma.droneBuild({id: buildId}).esc().esc()
  const vtx = await context.prisma.droneBuild({id: buildId}).vtx().vtx()
  const receiver = await context.prisma.droneBuild({id: buildId}).receiver().receiver()
  const camera = await context.prisma.droneBuild({id: buildId}).camera().camera()
  const motor = await context.prisma.droneBuild({id: buildId}).motor().motor()
  const propeller = await context.prisma.droneBuild({id: buildId}).propeller().propeller()
  const frame = await context.prisma.droneBuild({id: buildId}).frame().frame()
  const antenna = await context.prisma.droneBuild({id: buildId}).antenna().antenna()
  const battery = await context.prisma.droneBuild({id: buildId}).battery().battery()