Hi! Did anyone get this error when starting a docker image? My introspection query works correctly generating my datamodel.prisma well, but then it's reporting this error when it's initializing and my playground doesn't show any query/mutation.

Is it possible to dump all data from database in prisma console?

commit

generated

files or not? - just wondering if there are any recommendations on that

Hey guys!

Can anyone help me?

Hi everyone

I need help

I have an existing mongo database

And I want to connect prisma in it

How can i do that ? because the prisma server always creating a new database when I deploy service in it

Hello guys!!! my team and I just awake with this issue, I have no clear where it came from, since yesterday everything was working fine, any idea? This is happening on local environments and deployed ones

Anyone have any luck with using different generated prisma typescript depending on whether the server is running locally, preproduction or production?

I need help, It is about Prisma Server

someone would help me?

Hello everyone. I'm trying to add user profile images to my react-native app with Graphcool. In the Graphcool docs GraphQL API / File management / File Uploading there's a link to a react-native-image-picker example. The link goes to a 404 GitHub page and I was just wondering if anyone knows where I can find that example.

Hi all, anyone has tried to implement i18n fields in prisma/graphql yoga using native code or plugins like i18next or similar?

Previously (as in, last year), I was using something like this in a query:

favourites: (_, { id }, context: Context, info) => {
    return context.prisma.query.user(
      {
        where: {
          id
        }
      },
      `
      {
        id
        favourites {
          id
          name
        }
      }
      `
    )
  },

I see that now, you’d instead use `context.prisma.user(...) but there’s no way of defining exactly what you want back. Is this intentional?

is there any roadmap for prisma? rly need to know the progress of prisma. currently, we need to decide, to stop implement prisma or go on with. i.E: No cascade delete possible with mongo, which is a no-go to do on api side

Thought renaming a type was going to be a nightmare but with the generated client + typescript it’s a breeze. Thank you Prisma team. 👍

Hi all graphql people :) If any of you happens to have or know a complex enough (so that I could copy it to production) project using

graphql-shield

with yoga/apollo, kindly share; I can't feel confident with auth without such help. Thanks to Prisma and such an active community :)

Hey @Harshit, is the Go caching feature I reported at https://github.com/prisma/prisma/issues/4029 planned? In general, is the development of the Go client (roughly) actively aligned with JS/TS? I feel like the Go client is always behind, also because pagination is missing (https://github.com/prisma/prisma/issues/4027)

Hello, Is there any projects or examples on how to implement background events with Prisma, such as when some resolver was called and an event triggered inside of it? Like I have a file which I need to process in the background after uploading. So a user uploads a file and after it was uploaded successfully I start an event in the background, make calculations and give him a new file.

Hello guys, I'm new with Prisma. There is a channel where I can ask something related to prisma examples? Thanks

I guess if Prisma dont support geo spatial queries (yet) but we can still query the database directly to achieve similar funcionality, right?

Hey guys, wondering how everyone is managing automated deployments with the newly created column that is required

Ummmm, Prisma doesn’t support mysql 8?

Guys at my work we have a php lumen REST API. It uses two databases MySQL and Mongo it is possible to use Prisma to interface with 2 databases?

Hello! What is currently the best way to communicate with a secondary prisma service? Scenario: I want to build multiple services and have them all use the same auth service. I want my public schema to hide the fact there are two services and present itself as a single service. Here is a mockup of my schema:

type Query {
  posts: [Post]
}
type Post {
  # this type is stored in my primary service
  text: String
  author: User!
}
type User {
  # this type is stored in the primary service too
  id: ID! @unique
  posts: [Post]
  accountId: ID! @unique
  account: Account!
}
type Account {
  # this type is stored in my secondary service
  id: ID! @unique
  username: String!
}