or is this a bad schema?

Hey guys. I am using prisma for a long time and so happy about it. But I have a problem, I am trying to use Prisma with Digital Ocean managed database. After following all instructions am getting an error:

WARNING: SQLException occurred while connecting to <http://db-postgresql-lon1-28856-do-user-3676973-0.db.ondigitalocean.com:25060|db-postgresql-lon1-28856-do-user-3676973-0.db.ondigitalocean.com:25060>
prisma_1  | org.postgresql.util.PSQLException: FATAL: database "postgres" does not exist

environment:
      PRISMA_CONFIG: |
        port: 4433
        # 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: postgres
            host: <http://db-postgresql-lon1-28856-do-user-3676973-0.db.ondigitalocean.com|db-postgresql-lon1-28856-do-user-3676973-0.db.ondigitalocean.com>
            database: defaultdb
            schema: public
            user: doadmin
            password: password
            ssl: true
            rawAccess: true
            port: 25060
            migrations: true

Looks like

database: defaultdb

is not passing to the config

has anyone used GraphQL-Voyager with their Prisma graphql endpoint and used the Introspection feature to visualize their schema?

If so, what did you paste into the introspection text area for your graphql endpoint to get it to work

Hi all - does prisma support wrapping a collection of API endpoints as its datasource? I don't have direct access to the DB layer, only a set of swagger endpoints over it

for those who would like to follow Nikolas's talk or any other talk live:

Hello everyone, Congrats on Prisma 2. I have some questions. Should i build projects in prisma 1 now? As prisma 2 is coming, It will bring some major changes, i see. But what about the support of prisma 1. Can we easily migrate to prisma 2. And one extra server for prisma, what about this? What if I want to have one extra server for each database and try to connect multiple database in one graphql api server(ex. Apollo Server)? Will it be possible?

Hi everybody

Error: Syntax error while parsing GraphQL query. Invalid input "USER)\r\n username: String! @unique\r\n email: String! @unique\r\n /", expected Value, Argument, Directive or FieldDefinition (line 9, column 31): role: Role! @default(value: USER)

This error is driving me crazy today, I have made some minor changes in my project and suddenly this is happenning

I can´t find anything related in google and everything seems ok in my code

Hope someone can help

better to copy&paste the whole file..

My type definition? Is this

enum Role { ADMIN CLIENT USER } type User { id: ID! @id role: Role! @default(value:USER) username: String! @unique email: String! @unique password: String! posts: [Post!]! @relation(link: INLINE) profile: Profile @relation(link: INLINE) updatedAt: DateTime! @updatedAt createdAt: DateTime! @createdAt }

I have had some issues lately since demo server migration to 1.32 beta, but these errors are in types definitions and I can't see what did I do wrong

Hello all, just wondering if anyone had some insight to this issue I'm having. When I run command prisma deploy and select demo server from terminal it freezes

This article about using Prisma + Now.sh says that it doesnt work for now v1 anymore (now is currently on v2) https://www.prisma.io/tutorials/deploy-a-graphql-server-with-zeit-now-cs04 any ideas how to do this now?

Nvm, solved

Hi

Error: Directive id: Couldn't find type id in any of the schemas.

😞

@Jovaanc you probably meant id: ID! @unique

Since updating to the latest prisma, graphqlgen is not properly updating generated/graphqlgen.ts with the new scalar field that I added to my datamodel.graphql. Anyone else having a similar issue?

Is there any issues about how to host graphql so subscriptions work correctly?

I'm afraid of lambda sockets

Hi, I have two containers, one running a Postgres database and the other running prisma server. I need a suggestion from some of you experts. Your experience would help me a lot. 1. Is it safe to run my postgres production Database in a Docker container, provided I take daily backups. We have around 100 users right now. The database is small, but critical. What problems could one face hosting the db in a container on one’s own? 2. Or should I consider DBaaS like RDS, DO Managed Postgres etc.