Hi there, i was trying Prisma and as a first impression after following the Quickstart I find it pretty awesome, so congrats and thank you for the work! 😊 I tried the example https://github.com/prisma/prisma-examples/tree/latest/typescript/graphql-nextjs later and following the

README.md

file I found some issues when I reach the

Profile

part. I explained them better in this issue https://github.com/prisma/prisma-examples/issues/2417 to see if someone could lend me a hand with them. I am posting it here just in case someone can help me faster or has any idea. By the way, sorry if this is not the proper channel for this kind of messages, if there is a more appropriate one please tell me and I would gladly post it there 😊

I once asked this question, but I would be curious to ask it again. In current CI/CD workflows (for example, deploying a docker container to AWS), I am always curious where in their process people include the actual migrations of the table. • Is this in the same docker image as where you serve the API from? The caveat is that you would have to include prisma/cli as dependency in your docker image only for migration-time (which might make the image much heavier)? • Do you use a separate image purely for the migration? And if so, when do you deploy this image?

I am currently going through the upgrade from Prisma1 to Prsima2 detailed here: https://www.prisma.io/docs/guides/upgrade-guides/upgrade-from-prisma-1/upgrading-the-prisma-layer-postgres and I am stuck on the part where I have to run the SQL queries (part 5). I have run the command

npx prisma-upgrade prisma1/prisma.yml prisma/schema.prisma

and have been given some SQL queries to run

ALTER TABLE "my-app-dev$dev"."Answer" ALTER COLUMN "id" SET DATA TYPE character varying(30);
ALTER TABLE "my-app-dev$dev"."Answer" ALTER COLUMN "createdForQuestion" SET DATA TYPE character varying(30);
...

I have executed these queries in several different DB clients and every time I re-run

npx prisma-upgrade prisma1/prisma.yml prisma/schema.prisma

it still prints me the same SQL queries that I have to run. I have checked the varchar length in my tables after running the scripts and they seem to show the correct value (30). Shall I assume this is a bug and continue on from here? Or does this mean something is still not correct with the schema?e

Hey, how can i run prisma migrate programmatically when deploying to heroku, right now i have to run the heroku console from the web app, and run

npx prisma migrate

, i'm building everything in docker.

If I'm trying to search a text[] column, do I want to use something like column_name: { contains: [search_text]} in the where clause?

I'm having an issue with connectOrCreate - specifically, this:

(node:15954) UnhandledPromiseRejectionWarning: Error:
Invalid `prisma.runs.create()` invocation in
/mnt/c/Users/me/wd/helios/commands/functions/sale.js:56:38

   52 }
   53
   54
   55 async function insertRun(msg, obj) {
→  56     const newRun = await prisma.runs.create(
  Error occurred during query execution:
EnvVarNotFound("Expected parent binding \'2\' to be present.")
    at qw.request (/mnt/c/Users/me/wd/helios/node_modules/@prisma/client/runtime/index.js:210:203)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async insertRun (/mnt/c/Users/me/wd/helios/commands/functions/sale.js:56:20)

However, the only thing that has a value of 2 isn't it - I've changed it multiple times, still returns the error with 2.

Are you able to have a Connect inside of a ConnectOrCreate?

Users_Runs_ad_idToUsers: {
                connectOrCreate: {
                    where: { discord: obj.ad.id },
                    create: { 
                        Servers: {
                            connect: { server_id: await getServer(obj.ad.nickname) }
                        },
                        discord: obj.ad.id,
                        payout_char: obj.ad.nickname,
                        balance: 0,
                        Ranks: {
                            connect: { id: 4 }
                        }
                    }
                }
            }

Something like this

I’m having some issues with doing a many-to-many inside a graphql resolver. I got this prisma schema: pretty much users can belong to several orgs and orgs can contain several users.

And schema for graphql (using graphql tools)

The issue is that in my resolver for users. If I include organizations like this:

And then resolve orgs by returning that part:

it works when client is requesting organizations on the query. Something like this: query { users { id email organizations { name } } }

Then prisma makes 3 queries to the database

The issue is that if the client only requests user info and not nested info about organizations

then prisma still does all 3 queries even if it is not needed

it would be enough with just 1 query

any idea how to solve it in a more efficient way so im not doing unecessary database queries?

Hello everyone

Any progress with this feature? https://github.com/prisma/prisma/issues/5079

Needing this so much right now that I'm considering migrating from Prisma to another lib

Hey guys, I'm having trouble getting started with the Rust FaunaDB crate Having an error with the following code:

let obj = {
    let obj = Object::default();

    obj.insert("id", store.id);
    obj.insert("active", store.active);
    obj.insert("paid", store.paid);

    obj;
};

let query = client.query(Create::new(Ref::class("stores"), obj));

With the error:

21 |         let query = client.query(Create::new(Ref::class("stores"), obj));
   |                                  ^^^^^^^^^^^ the trait `std::convert::From<()>` is not implemented for `faunadb::prelude::Query<'_>`

EDIT: Nevermind... I relalised I had a dumb mistake. My function was:

pub fn new(client: &Client, &store: &Self) {

But should've been:

pub fn new(client: &Client, store: &Self) {

It seems like the FaunaDB Rust crate is abandoned 😞

Hi all! Excited to be part of the community. I'm pretty new to prisma. Have mostly been using knex.js in the past. I really like Prisma so far as I've experimented but my big concern is the lack of a production ready migration feature.

How are other people using Prisma in production if

prisma migrate

is still not production ready?

I know prisma is a new way to think about ORM's so I'm curious if I'm missing something.

Are there any benchmarks for prisma to compare to typeorm and/or mikro-orm?

Hi! I'm trying to setup Jest tests but I have a problem with connection to DB. I get an error:

error: Environment variable not found: DATABASE_URL.

despite the fact I have it in my

prisma-test-environment.js

(like in the examples directory). Can somebody help me with that?

Hi, im trying to do a delete with multiple parameters. Seems kinda weird that the where field is only for unique columns. I have to do a query first to query the record. Then another query to delete the record itself? Is there a better eay to do this?

How can I create my datamodels as PascalCase but keep my actual PG database tables/columns as snake_case?