How do I create a scalar type Numeral(30,2) on Postgres via Prisma datamodel? Default Prisma Float type is Numeral(65,30). I changed a field type manually on Postgress to (30,2). Prisma couldn’t connect to the db after that.

Hello, can i post here something that i think is a bug ?

this is the link to the error https://stackoverflow.com/questions/56049813/prisma-deploy-embedded-in-two-fields-error-like-bug

Two field with the same embed throws an error

Hi, neither the pre configured droplet nor the fargate server were able to connect. Still just refusing to connect on port 80. Has anyone had success with either of these tutorial?

Could anybody explain to me how Docker works with Prisma? I'm having difficulty understanding the relationship between the two.

Anyone else having timeout issues committing to prisma?

something I find super inconsistent about Prisma is enum naming. if I try to make an enum in datamodel.prisma with a lowercase character it says:

The first character of each value must be an uppercase letter.

. although when you auto-generate a schema.graphql all the enums are lowercase like this:

enum DeviceOrderByInput {
  apnsToken_ASC
  apnsToken_DESC
  createdAt_ASC
  createdAt_DESC
  fcmToken_ASC
  fcmToken_DESC
  id_ASC
  id_DESC
}

why the inconsistency and any way to make it consistent?

Hello guys, how do i go about this PRISMA_MANAGEMENT_API_SECRET error while trying to re-deploy my prisma server, haunted me for the last many hours now

Hi guy, how to show sql queries that are executed by prisma. I follow this issue: https://github.com/prisma/prisma/issues/2833 but it doesn't work.

🔥This is great, Awesome Prisma (https://github.com/catalinmiron/awesome-prisma) was merged in the main Awesome repository ❤️. If you'd like to share some great resources don't hesitate to open a PR, you're more than welcome! 🙌

any way to for prisma deploy to skip sending data to

prisma.sh

? currently stuck with this for an offline-installation:

2019-05-09T11:41:50.549Z environment { needsAuth: false }
2019-05-09T11:41:50.551Z client is local cluster: false
2019-05-09T11:41:50.555Z client Sending query to cloud api
2019-05-09T11:41:50.556Z client <https://api2.cloud.prisma.sh>
2019-05-09T11:41:50.556Z client {
      me {
        id
        name
        login {
          email
        }
      }
    }
2019-05-0

Java heap space issues.. can i give prism more heap space?

Is it possible to limit the number of results in a nested, relationed field? E.g. something like:

query foo {
foo(first: 1) {
    id
    bar(first: 10) {
      id
    }
  }
}

Where the

foo

schema has a property

bar

whose value is

[bar]

Or is that trying to do too much in a single query

Figured it out: Had to add parameters to the Type definitions for the nested connections. Didn’t realize that was possible outside of a

Query

Hi guys! I know I can use the Prisma demo database, but how do I go about migration to my own self-hosted database or Heroku through Prisma cloud?

Is it possible to catch mutation errors on the server level in a try catch? I have a yoga server with a mutation in a try/catch block but it seems like the code in the catch doesn’t run when error occurs

What I’m trying to do is insert an order record with a unique order number in the database, but “catch” if graphql throws a unique constraint violation error so I can generate a new order number and try again. I could always query the db when generating the # but I figured it was an unnecessary operation

@jdoyle112 I think I ran into the same issue and for some reason I was only able to get/catch the error by doing something like

await prisma.createFoo(args).catch(err => handleError(err))

It seemed like only promise-chaining the catch would work whereas with a try/catch block it never got to the catch

Interesting.. okay thanks @Craig

Is this place appropriate to ask about nexus-prisma issues?

I've got Prisma connected to my MongoDB. But when I make a

createUser

mutation, a new database is being created called

default_default

and the user is added there instead of the database I specified when connecting.

docker-compose.yml

version: '3'
services:
  prisma:
    image: prismagraphql/prisma:1.23
    restart: always
    ports:
    - "4466:4466"
    environment:
      PRISMA_CONFIG: |
        port: 4466
        # uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
        # managementApiSecret: my-secret
        databases:
          default:
            connector: mongo
            uri: '<mongodb://host.docker.internal:27017/name-of-db>'

Anyone can point me in the right direction of using passport-twitter as a way to authenticate with prisma?

Has any one successfully migrated their project over to using nexus-prisma? I’m having some trouble setting up my queries and mutations and would love some help. Thank you!

Anyone got an idea on this?

Why, when using nexus-prisma, am I seeing this kind of error when firing a mutation?

{
  "data": null,
  "errors": [
    {
      "message": "Expected Iterable, but did not find one for field Mutation.signup.",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "signup"
      ]
    }
  ]
}

I can fix it by wrapping my return (a token and user object) in an array but I’m not sure why it’s expecting an array.