Hello

Everyone

I'm Momin from Dhaka Bangladesh

Good morning 🌞 @everyone

Hi @Momin I’m also from Dhaka Bangladesh

Great @Naimur Rahman

Good to know

Connect with me @Naimur Rahman Facebook

Facebook/mominriyadh

Okay brother.

Where do you live in Dhaka

?

I live in Khilkhet, Nikunja-2. You?

I have an array of strings (Prisma 1) and I want to push a string in it, but the only available method is

set

. Is there a way to push a string in the array without querying the strings that are already there?

I was just watching some of the Prisma Day videos and had a question. It was mentioned that you can update your Prisma Schema directly to change a

User

relationship to the name

Author

on

Posts

. My question is, if you do this, and then re-run an introspection, will it blow away your changes? Or does it do a diff and intelligently update the schema file?

Hey guys, has anyone used prisma migrations with docker or inside a private network? I'm wondering what would be the best way to apply migrations. Maybe its possible to check if there is a new migration and apply it on startup?

This also opens the question, how do you do migrations on different services that use the same schema and db?

Hi guys, Thans for let me in, Im so happy for being here.

Guys, I'm implementing prisma server in an existing project, I'v being working around one week, I've read documentation but I can't expose the data from my Aws RDS. can anybody help me. thanks in advance.

Is there an example of using prisma with the connection plugin (https://nexus.js.org/docs/plugin-connection)?

Is there a list anywhere of notable projects/companies using Prisma? I’m considering it for our upcoming backend rewrite, but to be honest it’s relative newness gives me pause, compared to namely Django which is quite mature, battle tested, and relied on by many

Thanks for the stickers, Prisma team! 🙏

Hi, just wondering if anyone else is experiencing any problems with creating new servers using Prisma.io? I've been getting a "GraphQL error" saying I provided invalid credentials whenever I try to spin up a database and a server using the Heroku integration.

hi, how do i implement the aggregate/sum ?

Hey, if any of ya could give a quick hint on this I'd greatly appreciate it! OR is driving me mad https://github.com/prisma/prisma/discussions/3030

Do the executeRaw and queryRaw template tags escape/sanitize the interpolated variables? I’d assume so, but I just want to check

Hey! Sorry for bothering you guys, but i was hoping to find some help here. I am using PostgreSQL in combination with Prisma2 and i am trying to cascade delete. What i found on google was that i need to cascade on database level - unlike in prisma1. My Table looks as follows

CREATE TABLE presets (
    id SERIAL PRIMARY KEY,
    uid character(5) NOT NULL REFERENCES tokens(uid) ON DELETE CASCADE,
    deviceid integer NOT NULL,
    data jsonb NOT NULL,
    synced smallint NOT NULL DEFAULT 0,
    isdeleted boolean NOT NULL DEFAULT false,
    lfid integer,
    error jsonb
);

Now when i am trying to delete a row on said

tokens

table

await prisma.tokens.delete({
	where: {
		uid
	}
});

it gives me an violation error

Invalid `prisma.tokens.delete()` invocation in
path/dist/data.js:314:84


  The change you are trying to make would violate the required relation 'tokens' between the `presets` and `tokens` models.
    at PrismaClientFetcher.request (path/node_modules/@prisma/client/runtime/index.js:1:185690)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  code: 'P2014',
  meta:
   { relation_name: 'tokens',
     model_a_name: 'presets',
     model_b_name: 'tokens' } }

I am quite confused on what i am doing wrong, any tips appreciated.

hi there I have a problem in Prisma 1 when I run script deploy as "deploy": "prisma deploy --env-file .env" in package.json the are some error ERROR: graphqwith%20prisma is an invalid service name. It must be less than 140 characters and can only contain alphanumeric characters and -.

Hi folks, I have a general question regarding the nr of database calls when using prisma in a graphql app (Nexus schema based). Are there strategies or so for accomplishing Scenario 1 in the following example in a clean way:

# Scenario 1: Do a single Prisma call on Posts-level (Level A)
{
    posts { # <-- Level A: Do a single prisma.many call, and actually include all users, profilePictures, with all of their
        users { # <-- Level B❓On the user-resolver, do we then have to do a superfluous another call (even if level A already got all of their info?)
            name
            title
            birthDate
            derivedNrOfFriends
            profilePictures {  # <-- Level C ❓On the profilePictures resolver, do we do a call even if the posts already included everything necessary?
                ...etc
            }
            friends {

            }
        }
    } 
}

# Scenario 2: Do multiple Prisma call on each resolver (Level A, Level B, Level C)
{
    posts { # <-- Level A: Do a prisma.many call, only include post fields
        users { # <-- Level B❓Do a prisma.many call, only include user fields, use optionally parent.id to scope on posts
            name
            title
            birthDate
            derivedNrOfFriends
            profilePictures {  # <-- Level C. Do a prisma.many on profilePictures resolver level, use optionally parent.id to scope on users
                ...etc
            }
            friends {

            }
        }
    }    
}

I am getting an error while doing

prisma deploy

. The error says

You are updating the field _permissions_ to be required. But there are already nodes for the model _User_ that would violate that constraint

What does this really mean? Here is how my

user

model looks like:

type User {
  id: ID! @id
  email: String @unique
  firstName: String!
  lastName: String!
  isActive: Boolean! @default(value: true)
  isVerified: Boolean! @default(value: false)
  isUsingSystemPassword: Boolean! @default(value: true)
  userType: UserType @default(value:Admin)
  password: Password! @relation(name: "UserPassword", onDelete: CASCADE)
  projects: [Project] @relation(name:"UserProjects", onDelete: CASCADE)
  productFeedback: [ProductFeedback] @relation(name: "ProductFeedback")
  permissions: Permissions! @relation(name: "UserPermissions", onDelete: CASCADE)
  createdBy: UserCreationMap! @relation(name: "CreationMap", onDelete: CASCADE)
}

and how my

Permissions

models looks like

type Permissions {
    id: ID! @id
    createUser: Boolean! @default(value: false)
    editUser: Boolean! @default(value: false)
    deleteUser: Boolean! @default(value: false)
    viewAllUsers: Boolean! @default(value: false)
    userId: User @relation(link: INLINE, name: "UserPermissions")
}