Hi, I’m using Postgresql with Primsa. I need some help with the best way to design my database. More details inside the thread.

I’m working on the HowtoGraphQL Hackernews tutorial. When I do a migrate I see this warning in the console:

warn(prisma) @prisma/cli has been renamed to prisma.

Please uninstall @prisma/cli: npm remove @prisma/cli

And install prisma: npm i --save-dev prisma

Hey all, I'm wondering if someone can explain self relations by use of a join table. I know has been discussed previously but there's something I'm still missing some important about how it works. The use-case here is having a

User

model where it can have friends who are also users. About 5 months ago I saw a nice explanation by @Ryan where he said we could use the following model:

model User {
  id        String         @id @default(cuid())
  createdAt DateTime       @default(now())
  updatedAt DateTime       @updatedAt
  friends   Relationship[]
}
model Relationship {
  id        String   @id @default(cuid())
  user      User?    @relation(fields: [userId], references: [id])
  userId    String?
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

I think the thing that would clear this up for me would be to see example prisma create commands that would show how to take 2 users and first create a relation from

user1 -> user2

and then how to do the back relation. I'll start- thanks so much!

const user1 = await prisma.user.create({ data: { id: "1" } })
const user2 = await prisma.user.create({ data: { id: "2" } })
const relationship1To2 = await prisma.relationship.create({ //?? })
const relationship2To1 = await prisma.relationship.create({ //?? })

(My confusion stems from the fact that it seems like if we create a relationship where we set

user1.id

to

userId

, we will establish the relationship between

user1->friendship

but not back to

user2

.)

Hey friends 👋 as you might have seen, we've launched Prisma Migrate for General Availability today 🚀 To help spread the word about Prisma Migrate, we'd very much appreciate if you could help us out with a retweet ❤️ https://twitter.com/prisma/status/1371861835184533512

I”m working through the HowToGraphQL tutorial. I’m in the section: Adding a Database > Getting Started with SQLite. When I run:

npx prisma migrate dev --preview-feature

I see this message in the console:

migrate dev is not a prisma command.

▸ Perhaps you meant generate

Prisma Migrate entering GA is huge. Congratulations all, I will be deploying a production implementation of prisma migrate now very soon :)

I am really excited about Prisma Migrate going GA. Congratulations to the teams and amazing community behind Prisma. 🎉

Hi all. Does anyone know how to disable the admin dashboard that can be accessed through http://localhost:4466/<project>/dev/_admin ?

Hi, I have an application depending upon

graphql-yoga

but due to update in Chrome, it doesn't allow to persist

cookie

by

sameSite

which can be fixed by https://github.com/prisma-labs/graphql-yoga/issues/623 I would be happy to contribute to fix it if the mentor aggrees, and community is active. Thanks!🙂

Hey all. Is it possible to tell Prisma that use relation but not actually create foreign keys in the database? It’s all good, but my db is getting bigger, and I don’t want to worry about foreign keys during the scaling phase. My thought, since I am declaring all the relation explicitly, so Prisma would figure it out without relying on the FKs. And I know the data consistency is my problem now. I haven’t tried dropping FKs manually, I’ll try that as well, but I just wanted to ask initially just if possible,

I've only used

prisma db push

so far, now

prisma migrate dev

wants to reset the database but I already have data in it. How can I keep it or easily copy it?

Hey everyone, I had a question about connecting to remote sql or mariadb instance, I was wondering how you typically format your connector. Right now I am getting a connection error and I believe it's trying to connect locally even though I have a hosting ip indicated. Any assistance would be great.

Hello! When deploying via Vercel with 2.18, I'm seeing seed data in a production environment. Do seeds run by default?

Hi all! I have a question about Prisma seeding. I realize the scope of the question may be somewhat outside Prisma itself, but would appreciate any help/pointers if anyone is willing to offer some. We use Next.js, and following the 1.18.0 release I added

"ts-node": "ts-node --compiler-options '{\"module\":\"CommonJS\"}'"

to

package.json/scripts

to allow it to run. Prior to 1.18.0 I was using the workaround suggested in this GitHub issue by elkevinwolf. All was working fine on my local dev environment, but I’m getting errors when I try to do this as part of a Vercel build. The

seed.ts

file references other lib files in our codebase, almost all of which are ES6 modules. We also have baseUrl set to

.

in

tsconfig.json

– though I think I’ve been able to work around that. I feel that this is a result of my knowledge gap in how modules and compilers function – but since I reference ES6 modules and they have import statements, etc. all with absolute imports utilizing the basePath, things break as those functions get invoked. I’m sorry if this is somewhat vague, happy to provide code examples/errors/etc. – just want to make sure I provide what’s useful.

Another Q: is there a preferred way in

package.json

to toggle migration commands when deploying? I.e. to run

prisma migrate dev

vs

prisma migrate deploy

dependent on environment (preview vs prod)?

I’m working through the React GraphQL Apollo tutorial. I’m on Introduction > Exploring the server. When I run the sample GraphQL query I get:

“code”: “INTERNAL_SERVER_ERROR”

“Argument id for data.postedBy.connect.id must not be null. Please use undefined instead.\n”

Looks like it’s a problem in:

/@prisma/client/runtime/index.js:32448:19

I’m the Mutations: Creating Links section of the React Apollo Tutorial. The CreateLink component gives an error:

Unhandled Rejection (Error): Argument id for data.postedBy.connect.id must not be null. Please use undefined instead.

I’m guessing this because you need to be logged in before you can post? Is it possible to modify the server code to allow

postedById

to be undefined or null?

Wondering if there's a way to update multiple nested records in the one statement, with each nested record having it's own set of data. Like by providing an array of posts in this example https://www.prisma.io/docs/concepts/components/prisma-client/relation-queries#update-a-specific-related-record. Eg something like:

const update = await prisma.user.update({
    where: {
      id: 6,
    },
    data: {
      posts: {
        update: [
          {
            where: {
              id: 9,
            },
            data: {
              title: 'Posts 9 title',
            },
          },
          {
            where: {
              id: 10,
            },
            data: {
              title: 'Post 10 title is different',
            },
          },
        ]
      },
    },
  })

Hello! Is there any demo java graphql example project that contains also monitoring some alternative to apollo studio? Is it collecting metrics via Graphana and Prometheus?

Having some trouble with updating data with some nested creates and connects. Can someone help?

Having the current database table setup (User & Post) tables with a one-to-many relation on the User->Post I can't get the cascade delete to work, because of a relation conflict. What would be the way to go about this? (SQLITE) Error: "PrismaClientKnownRequestError2 [PrismaClientKnownRequestError]: The change you are trying to make would violate the required relation 'PostToUser' between the

Post

and

User

models."

Hi all! Happy to join the community 🙂 I am new to Graphql Yoga and would like to set up my server to support wss connections, can anybody help me with this? I have been readings the docs for a couple hours :/

I wrote a little bit about why I love Prisma and have used it exclusively for years now: https://twitter.com/mxstbr/status/1372483017722187776 😛risma-rainbow:

Hello all, general question 😄 How do you deal with i18n in your backend ?

Do you translate your error messages directly in the backend? Do you just send a code + default english message and handle it on the frontend?

I personally prefer to send back errors with code / keys in english and handle the i18n in the frontend 🙂

ok so you don’t have any i18n logic in your backend?

I think this is the easiest path and the one I’ll take 😄

I was starting to setup i18next for my graphql API with Nexus but I don’t think it’s worth it

My only i18n logic in the back end is related to multi lingual lists (genders, countries, etc...) which are saved as JSON fields like this

{
  "en": {
    "title": "Content"
  },
  "fr": {
    "title": "Contenu"
  }
}