can I define

Timestamp

not DateTime for createdAt/updatedAt ?

Hey folks! 👋 I was wondering if anyone could point me in the right direction: at our company, we're using a deployment platform whose one of the requirements is that we need to use egress proxy for connections outside of the container. Since we're still using prisma v1, the infrastructure looks as follows:

[User] -> [API layer] <=> [Prisma Query Engine]

How could I pass all the communication between API Layer (

graphql-yoga

server) and Prisma Engine through Proxy? I tried applying

http-proxy-middleware

into the

express

server layer but it doesn't seem working out for me.

is anyone but me experiencing that the Prisma server is super slow and inefficent and point of failure/bottleneck? I'm load testing our setup both locally and on AWS and I see the same thing: the Scala server is really slow. here's the output of

docker stats

whilst running the load test. I would expect postgres to be the bottleneck. why is the server doing all that work? running latest Prisma version. memory usage is perfectly fine btw. it's just CPU

Hi, does anyone know where the docs for

@id(strategy)

are? I don't see them anywhere in the

@id

part of the 1.34 docs https://www.prisma.io/docs/datamodel-and-migrations/datamodel-MYSQL-knul/

basically I'd like to make an ID optional on creation, but I can't seem to figure out how. Do I have to set

strategy: NONE

and always generate it in application code?

(I'm using cuids, by the way)

I run my prisma container with "docker-compose up -d" but when I open this url => http://localhost:4466 it's not responding. even I checked my container with "docker ps" there was not any problem with my container

Im having trouble wrapping my head around modeling a Group of Users, where one User is the Group owner

do i model the user with two Group fields (owner, memberIn) and the same in the group (Owner, members) or do i make a relation type in between that specifies the roles

Hi, how can I define a field for big integer of 64 bit in the data model? The integer field has max value of 2147483647, but I need to save a 64 bit integer into the postgresql database with the bigint type.

how can I read data with

group_by

?

Hello 👋 I was calling a db call in my mutation and the only thing I receive back is a Object null prototype and _typename: User, any clue what I might be doing wrong?

const { userId } = ctx.request;
    if (!userId) {
      throw new Error('You must be signed in soooon');
    }
    const users = await ctx.db.query.users({}, info);
    console.log(users);

[ [Object: null prototype] { __typename: 'User' } ]

Using Prisma datamodel 1.1, is

Subscription

really a reserved name? I get this error when trying to deploy:

The type 'Subscription' has is using a reserved type name. Please rename it.

How do i deploy after a database mistake ? some tables are missing, and prisma keeps rolling back because it cant delete the tables, even when using --force

Try

prisma delete

and then

prisma deploy

Hi guys, any one have success in config a Docker compose with the Prisma Server and a pgbouncer, that is pointing to a PostgresDB?

Is there any way to downgrade the development servers hosted by prisma to earlier versions?

Hey guys, I have an issue that I hope someone can help me out with. We have decided to switch to manual prisma migrations (after upgrading to 1.34), however, the CLI has an issue dealing with enums when running prisma deploy --no-migrate. It's showing me the error below:

Here is how it is defined in SDL:

And here is how the field is defined in DB itself:

Basically, it is doing that for all enums in our system

Hey all, does anyone have experience hooking up Prisma/React to a somewhat automated email dispatcher? We run a gaming site that I think would be cool to message users when events get populated. www.metacall.gg

Hi , Anyone already trying using prisma2 nexus enum ? I tried using enum and got same error as this thread https://www.prisma.io/forum/t/prisma2-with-nexus-no-subset-types-are-available-error/7387

Hello everyone

I have just updated my prisma version. Now when I try to deploy my new datamodel, it shows me the bellow error

OrderItem
    ✖ You are removing the field `updatedAt` while migrating to the new datamodel. Add the field `updatedAt: DateTime! @updatedAt` explicitly to your model to keep this functionality.
    ✖ You are removing the field `createdAt` while migrating to the new datamodel. Add the field `createdAt: DateTime! @createdAt` explicitly to your model to keep this functionality.

Even --force option does not help me in this case

Is Prisma 2 ready for production ( if I don't need any of the missing features ) ?