HI Everyone, what platform would you recommend to deploy Nexus? other than vercel

Hi all, I am trying to run "prisma generate --endpoint", because playground can not show my schema. But I end up getting the error: ▸ [WARNING] in /home/aa/workspace/aa/prisma.yml: A valid environment variable to satisfy the declaration 'env:PRISMA_ENDPOINT' could not be found. Downloading schema ! ▸ Cannot read property 'getToken' of undefined Get in touch if you need help: https://slack.prisma.io To get more detailed output, run $ export DEBUG="*" (node:28930) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated I can't really figure out where this error originates from. Any input is appreciated 🙂

Is there a way to findOne with two terms?

const winnerSearch = await prisma.entries.findOne({
            where: {
                user: winner,
                lotto_id: parseInt(x)
            }
        })

Gives me an error

Hey! Is it possible to run command for migrating up in code? For testing purposes, we create new DB for that test, we need to upload the current schema and create client with source (database link, i know this is possible). Thanks!

Hello Guys. How do we deploy prisma 2 if it doesn't support prisma cloud unlike prisma 1. I am new to prisma. I learned a tutorial in prisma 1 want to make a side project in prisma 2. Any help is appreciated. Thank you!

Hello everyone. Is the enum keyword scrapped in Prisma 2? I get this error when using Enum `error: Error validating: You defined the enum

Status

. But the current connector does not support enums.`

Hey all, I was wondering if it's possible for prisma to automatically convert bigint types to string?

Thanks for the reply. I managed to get rid of the file error, but when I try to click on the schema tab on playground, I just get an blank page. When looking at the console via developer tools I get the following errors:

How would be the recommended way to count a list that is linked using an indirect relationship? Looks like I can't do:

ctx*.*_prisma_*.*_user_*.*findOne({ where: { id: root*.*_id_ } })*.*_contacts.count(args)_

as

contacts.count

doesn't exist in that situation ----- Edit: I used

ctx.prisma.contact.count({ where: { user: { some: { id: root*.*_id_ } } } })

But idk if it's the correct/most optimized way of doing it

how do I check the existence of an entity before create a new one?

.prisma.[].create does not have this functionality. I used to use prisma.$exists.[] back in prisma 1

Careful when you guys introspect. I forgot I made some manual changes in my schema.prisma and blew things up 🤦

Hey peeps, does anyone know where to find better documentation on GraphQL.js? A lot of low-level functions seem to have no documentation such as

GraphQL*Type.toConfig()

Curious, is there a library for generating typescript types? Or do you just do magical string concat to generate them?

I keep getting a PrismaClientKnownRequestError: ...value for column is too long. Code: P2000

here is the complete error:

PrismaClientKnownRequestError: 
Invalid `prisma.user.create()` invocation in
/.../dev/resolvers/Mutation.js:25:36


  The provided value for the column is too long for the column's type. Column: <unknown>
    at PrismaClientFetcher.request (.../node_modules/@prisma/client/runtime/index.js:1:226003)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  code: 'P2000',
  meta: { column_name: '<unknown>' }
}

Good evening, I am working on following the Prisma tutorial. However I am confused about a couple of things. When I run

npx prisma generate --schema ./prisma/schema.prisma

I get an error saying

Syntax Error: Unexpected Name "datasource"

So then I ran the command like this part of the docs, but encountered an unknown flag

--schema

error! It has been really hard to figure out what is going on via Google. I have a folder in the root of my project called

prisma

that contains my

datamodel.prisma

prisma.yml

. Those files look like this:

# datamodel.prisma
datasource postgresql {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model Schedule {
    id Int @id @default(autoincrement())
    scheduledPhase ScheduledPhase @relation(fields: [phaseId], references: [id])
    phaseId Int
    name String?
    description String?
    startDate DateTime
    endDate DateTime

    @@index([startDate, endDate])
}

model ScheduledPhase {
    id Int @id @default(autoincrement())
    name String
    description String
    schedules Schedule[]
}

# prisma.yml
endpoint: ${env:PRISMA_ENDPOINT}
datamodel: datamodel.prisma
secret: ${env:PRISMA_SECRET}

generate:
  - generator: javascript-client
    output: ./src/generated/prisma-client/

hooks:
  post-deploy:
    - graphql get-schema -p prisma

Could I get some help figuring out how to get past this barrier, please? Thank you for any help in advance. This is my first time using Prisma and I think it would be really cool, if I can get it up and running. Debug output:

WARNING: Error: [WARNING] in /Volumes/DevDench/development/prisma-test/planning/prisma/prisma.yml: A valid environment variable to satisfy the declaration 'env:PRISMA_ENDPOINT' could not be found.
    at /Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-cli-engine/src/Output/index.ts:227:41
    at SimpleAction.ActionBase.pause (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-cli-engine/src/Output/actions/ActionBase.ts:81:22)
    at Output.warn (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-cli-engine/src/Output/index.ts:224:17)
    at Variables.warnIfNotFound (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-yml/src/Variables.ts:265:16)
    at /Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-yml/src/Variables.ts:107:20
    at bound (domain.js:426:14)
    at runBound (domain.js:439:12)
    at tryCatcher (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (internal/timers.js:456:21)
    at process.topLevelDomainCallback (domain.js:137:15)
WARNING: Error: [WARNING] in /Volumes/DevDench/development/prisma-test/planning/prisma/prisma.yml: A valid environment variable to satisfy the declaration 'env:PRISMA_SECRET' could not be found.
    at /Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-cli-engine/src/Output/index.ts:227:41
    at SimpleAction.ActionBase.pause (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-cli-engine/src/Output/actions/ActionBase.ts:81:22)
    at Output.warn (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-cli-engine/src/Output/index.ts:224:17)
    at Variables.warnIfNotFound (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-yml/src/Variables.ts:265:16)
    at /Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-yml/src/Variables.ts:107:20
    at bound (domain.js:426:14)
    at runBound (domain.js:439:12)
    at tryCatcher (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (internal/timers.js:456:21)
    at process.topLevelDomainCallback (domain.js:137:15)

Generating schema... !
Syntax Error: Unexpected Name "datasource"

GraphQL request:1:1
1 | datasource postgresql {
  | ^
2 |   provider = "postgresql"
    at syntaxError (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/graphql/error/syntaxError.js:15:10)
    at Parser.unexpected (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/graphql/language/parser.js:1463:41)
    at Parser.parseDefinition (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/graphql/language/parser.js:157:16)
    at Parser.many (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/graphql/language/parser.js:1518:26)
    at Parser.parseDocument (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/graphql/language/parser.js:111:25)
    at Object.parse (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/graphql/language/parser.js:36:17)
    at RelationalParser.DefaultParser.parseFromSchemaString (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-datamodel/src/datamodel/parser/parser.ts:31:20)
    at parseInternalTypes (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-generate-schema/src/index.ts:21:45)
    at generateCRUDSchema (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-generate-schema/src/index.ts:34:11)
    at Object.generateCRUDSchemaString [as default] (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-generate-schema/src/index.ts:64:22)
    at GenerateCommand.<anonymous> (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-cli-core/src/commands/generate/generate.ts:89:48)
    at step (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-cli-core/dist/commands/generate/generate.js:45:23)
    at Object.next (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-cli-core/dist/commands/generate/generate.js:26:53)
    at fulfilled (/Users/gkxdhr1/.nvm/versions/node/v12.16.1/lib/node_modules/prisma/node_modules/prisma-cli-core/dist/commands/generate/generate.js:17:58)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:15435) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
  output Exiting with code: 1 +0ms

Github issue is not sorting correctly on page load (not newest). https://github.com/prisma/prisma/issues

How would one use prisma to select only the first X out of find many? (code in replies_

This message was deleted.

Is this the right place to ask questions about

graphql-playground-react

?

Hi! Is there an official guide or tutorial on how to publish the server to heroku and how to manage the local vs the production endpoint?

In this post https://t.co/CCAF3STlPE it is also mentioned that Prisma Client could also be used with other languages in the future and that there is already an alpha version for Go. Are there plans to support other languages?

I’ll be going live in 2 hours for part 3 of the modern backend series. In this episode, I’ll go into the principles behind authentication and implement email-based passwordless authentication (with JWT) and authorization for the REST API implemented with Prisma, Hapi, PostgreSQL, and TypeScript.

I have a one to many relation between i.e. Product and Store. I can already create new Products that refer to their one Store like this: `` return await ctx.prisma.product.create({ data: { ..._data, // establish connection with store store_productTostore: { connect: { store_id }, }, }, }); ``

data

contains the input for the new

product

I checked the table it indeed refers to the designated home. However, I can't get the

products

column in Home to refer to the set of keys it has

products

is an array of the same type of key.id. I tried changing the above to this but it doesn't work: `` return await ctx.prisma.store.update({ where: { store_id }, data: { products: { create: { ...data } } } }); ``

Anyone use a particular workflow for ci/cd migration when merging pull requests? Eg automatically execute migration when setting new docker image

Reminder: Daniel’s livestream starts soon! fast parrot

Can anyone help me enter values for the many side of a one-to-many relationship?

Is it possible to orderBy a field randomly

I specifically do not want it asc or desc